PublicInput's Meetings module integrates with Microsoft Teams. This guide covers license and tenant requirements, IT-policy considerations, and the Microsoft Graph permissions PublicInput requests during authentication.

For Zoom setup, see Meetings Integration Guide — Zoom. For a comparison of all supported conferencing backends, see Tech Requirements for Meetings.

How It Works

PublicInput creates a standard Microsoft Teams meeting on the connected admin's Outlook calendar. A Teams join link is automatically attached. This is a standard Teams meeting — not a Teams Live Event — so requirements are simpler than you might expect.

License Requirements

The admin account used to connect must have a Microsoft 365 license that includes Exchange Online and Teams. Any of the following works:

Microsoft 365 Business Basic, Business Standard, or Business Premium
Microsoft 365 / Office 365 Enterprise E1, E3, E5 (or F3 for frontline workers)
Microsoft 365 A1/A3/A5 (Education)
Microsoft 365 Government G1/G3/G5 — GCC supported; GCC High and DoD not supported (see below)

Not required: Teams Premium, Teams Live Events, or Microsoft Stream licensing.

Not supported: Guest or external Microsoft accounts as the host — the connecting account must be a full member of its tenant. Microsoft 365 GCC High and DoD tenants are not currently supported (these run on Microsoft's sovereign Azure Government cloud, which uses separate endpoints from our integration). Standard Microsoft 365 GCC tenants are supported — see the section below.

Microsoft Graph Permissions PublicInput Requests

When an admin connects their Microsoft account to PublicInput, the following Microsoft Graph permissions are requested. Share this list with your IT team when they're reviewing the integration.

Delegated permissions (acting on behalf of the signed-in user)

User.Read — sign in and read the user's profile
openid — sign users in
profile — view the user's basic profile
email — view the user's email address
offline_access — maintain access to data the user has granted (enables token refresh without re-prompting)
People.Read — read the user's relevant people list
Calendars.Read — read user calendars
Calendars.ReadWrite — full access to user calendars (this is how PublicInput creates the Teams meeting event)
OnlineMeetings.Read — read the user's online meetings
OnlineMeetings.ReadWrite — read and create the user's online meetings
Group.ReadWrite.All — read and write all groups (admin consent required)

Application permissions (service-to-service, no signed-in user)

CallRecords.Read.All — read all call records, used for post-meeting reporting and analytics (admin consent required)

Azure AD app identifier

Application (client) ID: ddc35eef-c015-45fb-91df-21ff4c779417

IT administrators can use this client ID to locate the PublicInput app in Azure AD / Entra ID when granting admin consent or adding the app to Conditional Access allowlists.

Graph API endpoints used

GET https://graph.microsoft.com/v1.0/me/calendar/calendarView — list calendar events
POST https://graph.microsoft.com/v1.0/me/calendar/events — create a new Teams meeting event
GET https://graph.microsoft.com/v1.0/me/ — get user profile
GET https://graph.microsoft.com/v1.0/organization — get organization display name

Microsoft 365 Government Cloud Support (GCC vs GCC High)

Microsoft offers several government cloud tiers, and they are not all the same when it comes to third-party app integration:

Microsoft 365 GCC (Government Community Cloud) — Supported. GCC tenants run on Microsoft's worldwide commercial Microsoft Graph endpoints (the same endpoints our integration uses). If you are on standard GCC (G1/G3/G5 Government licensing), our Microsoft Teams integration will work for you.
Microsoft 365 GCC High and DoD — Not currently supported. These tiers run on Microsoft's sovereign Azure Government cloud (login.microsoftonline.us / graph.microsoft.us), which is a separate, isolated environment from the commercial cloud. Authentication tokens are not interchangeable between the two clouds, so our multi-tenant app cannot connect a GCC High or DoD tenant today.

If you are on GCC, expect the following from your IT department:

An IT administrator will most likely need to grant admin consent for the PublicInput app — most GCC tenants restrict third-party app consent to admins (rather than letting individual users approve apps).
Conditional Access policies in GCC tenants tend to be stricter (MFA, IP allowlists, device compliance). Your IT administrator may need to add the PublicInput app to their list of approved cloud apps before users can complete the connection.

For the technical details, see Microsoft's official documentation on Microsoft Graph national cloud deployments.

Connecting Your Microsoft Account

To connect your Microsoft Teams account:

Go to Meetings Admin → Connected Services in PublicInput.
Click Connect next to Microsoft Teams and sign in with your Microsoft 365 account.
You may be prompted to grant permission for PublicInput to read your calendar and create meetings on your behalf. If your organization requires admin consent, an IT administrator may need to approve the connection first.

Note: Each admin connects their own Microsoft account individually. If you need to switch accounts, remove the existing connection first on the Connected Services screen.

Tenant / IT Policy Requirements

The connecting user must be permitted to sign into third-party apps (no Conditional Access policy blocking the PublicInput app). Some tenants require an IT administrator to pre-consent on behalf of the organization.
The user's Teams meeting policy must allow creating private (non-channel) meetings. This is the default for most tenants.

System Requirements

For attendees joining a Teams meeting created by PublicInput, the standard Microsoft Teams client requirements apply. For the meeting host (the admin running the PublicInput meeting):

Any supported Teams client: Teams desktop (Windows 10+ / macOS), Teams web client (Chrome, Edge, or Firefox — latest two major versions), or Teams mobile (iOS / Android — latest two major versions)
For livestreaming Teams audio/video to the public via PublicInput, see Tech Requirements for Meetings

Phone / Dial-in

Teams provides its own audio conferencing dial-in numbers. PublicInput's phone bridge is independent and can be layered on top — particularly useful if the Teams tenant does not have a Microsoft Audio Conferencing add-on.

How PublicInput's Phone Bridge Works with Teams

PublicInput does not use Teams' auto-generated Audio Conferencing number for public callers. Instead, PublicInput's dedicated dial-in operates its own branded entry point and connects callers into the full meeting workflow.

Microsoft's auto-generated number drops a caller into the Teams audio stream with no additional functionality. PublicInput's number unlocks:

Branded / local numbers — a recognizable local area code constituents can trust
IVR + speaker queue — callers are prompted and routed into the same queue as online, SMS, and in-person commenters
Caller identification + registration — callers can register by phone so staff sees who's on deck, not just a phone number
Unified multi-channel queue — phone, SMS, web, and in-person comments all appear in one ordered speaker list
Recording, transcription, and AI minutes — PublicInput's transcription pipeline runs independently of Teams' recording policies
Compliance and analytics — audit-ready call logs and engagement analytics for open-meetings compliance
No Microsoft Audio Conferencing license required — agencies don't need per-organizer Microsoft add-ons to get a working public dial-in

Raise-hand and the PublicInput queue

Teams' raise-hand and PublicInput's public comment queue operate independently. We recommend directing the public to PublicInput's queue, and keeping Teams raise-hand for panel or staff use.

Recordings

Teams recordings follow your organization's Teams/Stream retention policy and remain in the Teams cloud. PublicInput captures its own independent recording and produces a speaker-aligned transcript and AI minutes separately.

Known Limitations

One connected Microsoft account per admin. To switch accounts, remove the existing connection on the Connected Services screen first.
GCC High and DoD not supported. Standard Microsoft 365 GCC is supported — see "Microsoft 365 Government Cloud Support" above.
Guest accounts cannot be used as the host. The connecting account must be a full member of its home tenant.
No live captions handoff from Teams. PublicInput's transcription pipeline runs independently from Teams' own caption/transcript features.
Reconnect required if the connection expires. If the Microsoft Teams card in Connected Services shows a yellow "reconnect" banner, you'll need to re-authorize the connection. New meetings will not be created automatically until the connection is restored.

Meetings Integration Guide — Microsoft Teams