- Before you begin
- Step 1: Open the Microsoft Teams setup in MeetingHub
- Step 2: Register an application in Microsoft Entra ID
- Step 3: Add the redirect URI
- Step 4: Add the Microsoft Graph permissions
- Step 5: Create a client secret
- Step 6: Paste the keys into MeetingHub and save them
- Step 7: Authorise MeetingHub to connect Microsoft Teams to WordPress
- Step 8: Confirm Microsoft Teams is connected to WordPress
- What attendees see
- Troubleshooting
- AADSTS50011: The redirect URI does not match
- AADSTS50194: The app is not configured as a multi-tenant application
- "Sign-in did not finish. Check that the Client ID, Client Secret and Redirect URI in your app match the ones shown here, then try again."
- "Authorisation did not complete. Try again."
- "This sign-in link has expired. Please start the Microsoft Teams connection again."
- "Sign-in needs https" or "Sign-in will fail with Plain permalinks"
- The meeting page says "No join link available"
- The sign-in still fails
- Frequently asked questions
- Security best practices
- You're ready to create Teams meetings
To connect Microsoft Teams to WordPress, register an app in Microsoft Entra ID, add your MeetingHub redirect URI and a client secret, then paste the Client ID and Client secret into the Microsoft Teams card in MeetingHub > Integrations > Video platforms and click Authorise with Microsoft Teams. After you sign in once, MeetingHub creates Teams meetings on your Microsoft 365 calendar for the events you schedule and for every booking made on a Teams booking page.
MeetingHub talks to Microsoft through Microsoft Graph, with an app you register in your own organization. Nobody else sits between your site and Microsoft.
By the end of this guide, you will have:
- An app registration in Microsoft Entra ID with your MeetingHub redirect URI
- The Microsoft Graph permissions MeetingHub uses
- A client secret, with its Value saved in MeetingHub
- Your Microsoft account authorised, with a green Connected badge in MeetingHub
- A clear picture of what attendees see on a Teams meeting page
Estimated setup time: about 5 minutes. Your Microsoft 365 work or school account already includes Microsoft Entra ID, where you register the app.
Before you begin #
Make sure you have:
- A Microsoft 365 Business or Education account (a work or school account) to organize the meetings. Personal Microsoft accounts can sign in, but Microsoft does not give them Teams meeting links.
- Permission to register apps in Microsoft Entra ID, at least the Application Developer role. If your organization limits app consent, an administrator may also need to approve the permissions.
- An administrator account on your WordPress site
- A site served over HTTPS. Microsoft only accepts
httpsredirect addresses for real domains. - Pretty permalinks (anything other than Plain in Settings > Permalinks). Microsoft sends you back to an address that needs them.
Let’s get started.
Step 1: Open the Microsoft Teams setup in MeetingHub #
Everything MeetingHub needs from Microsoft goes into one panel. Keep it open in its own browser tab while you work in the Microsoft Entra admin center.
- In the WordPress admin menu, go to MeetingHub > Integrations.
- Click Video platforms in the category list on the left.
- On the Microsoft Teams card, click Connect.

A panel titled Set up Microsoft Teams opens on the right, with three steps at the top: App keys, Authorise and Ready.
- Under Which Azure app?, click Where do I get these IDs? to open a four-step checklist of this guide, with your site’s redirect URL.

Tip: You can open the same panel from MeetingHub > Meeting setup > Platforms: click Microsoft Teams, then Connect Microsoft Teams. Once it is connected, the same button reads Connection settings.
Now comes the main part: registering the app with Microsoft.
Step 2: Register an application in Microsoft Entra ID #
Steps 2 to 5 happen in the Microsoft Entra admin center. Microsoft changes these screens from time to time, so if a label differs from what you see, look for the closest match.
- In the checklist, click Open next to Open the Azure portal, or go to
https://entra.microsoft.com/and sign in with the account that manages your organization. - If you have access to more than one tenant, use the Settings icon in the top menu to switch to the tenant where you want the app.
- In the left menu, go to Entra ID > App registrations. You will see the list of apps already registered in your organization.
- Select New registration. A registration form opens.
- In Name, type
MeetingHub. People see this name when they approve the app, and you can change it later. - Under Supported account types, open the drop-down and select Multiple Entra ID tenants. Any Entra ID Tenant + Personal Microsoft accounts works too.
- If the form also asks for a redirect URI, leave it empty for now. You add it in Step 3.
- Select Register.
Important: Do not choose Single tenant only, even though Microsoft suggests it for most apps. MeetingHub signs in through Microsoft’s shared sign-in address, which a single-tenant app refuses with an AADSTS50194 error.
Microsoft opens the app’s Overview page. You will see the Application (client) ID there, a long code of letters and numbers. Leave this page open; you copy that ID in Step 6.
Step 3: Add the redirect URI #
After you approve access, Microsoft sends you back to this address. Microsoft only accepts addresses you register in advance, so it must match the one MeetingHub uses, character for character.
- Go back to the MeetingHub tab. In the checklist, under Add the redirect URL below to it, click Copy.

The URL looks like this:
https://brightpath.example.com/mhub-msteams-oauth/
Your actual URL may look different. Always copy it from your own MeetingHub settings.
- Go back to the Microsoft Entra admin center. On your app, under Manage in the left menu, select Authentication.
- Open the Redirect URI configuration tab.
- Select Add Redirect URI. A pane titled Select a platform to add redirect URI opens, with one tile per app type.
- Select the Web tile. You will see a Redirect URI field and a Front-channel logout URL field.
- Paste the URL into Redirect URI. Leave Front-channel logout URL empty.
- Select Configure to save the redirect URI on your app.
Important: Choose Web, not Single-page application. MeetingHub signs in from your server, which needs a Web redirect.
Step 4: Add the Microsoft Graph permissions #
Permissions decide what MeetingHub may do in your Microsoft account. MeetingHub reads your profile, creates calendar events with a Teams link, and sets the room options on the Teams meeting.
- Under Manage, select API permissions. You will see the Configured permissions table, which already lists
User.Readfor Microsoft Graph. Microsoft adds it to every new app. - Select Add a permission.
- Select Microsoft Graph.
- Select Delegated permissions. MeetingHub acts as the signed-in user, so it needs delegated permissions, not application permissions.
- Under Select permissions, search for each of these permissions and tick it:
–Calendars.ReadWrite
–OnlineMeetings.ReadWrite
–offline_access
–openid
–profile - Select Add permissions.
- Check the Configured permissions table. It now lists those five Microsoft Graph permissions plus
User.Read.
If your organization requires an administrator to approve apps, select Grant admin consent for followed by your organization name, then select Yes. The Status column then reads Granted for followed by your organization name.
Note: OnlineMeetings.ReadWrite lets MeetingHub apply the lobby, attendee camera, attendee microphone and automatic recording options to each Teams meeting. Without it, meetings are still created, with Teams’ default options.
Step 5: Create a client secret #
The client secret is the password your site uses to prove it is your app.
- Under Manage, select Certificates & secrets.
- Open the Client secrets tab.
- Select New client secret. A short form opens.
- Add a description, for example
MeetingHub. - Choose when the secret expires. Microsoft allows up to 24 months and recommends less than 12.
- Select Add. The new secret appears in the list with its Value.
- Copy the secret’s Value right away. Microsoft never shows it again after you leave this page.
Important: Copy the Value, not the Secret ID. Only the Value works. MeetingHub’s checklist reminds you: Copy the secret Value, not its Secret ID. Only the Value works.
Tip: Note the expiry date. When the secret expires, Teams stops working in MeetingHub until you add a new secret and paste its Value.
Step 6: Paste the keys into MeetingHub and save them #
- In the Microsoft Entra admin center, open your app’s Overview and copy the Application (client) ID.
- In the MeetingHub tab, paste it into Client ID. It looks like
3fa85f64-5717-4562-b3fc-2c963f66afa6. - Paste the secret’s Value into Client secret.
- Tenant ID is optional. You can leave it empty.
- Click Save keys at the bottom of the panel. MeetingHub shows Keys saved. and moves to Authorise.

Save keys stays greyed out until Client ID and Client secret are both filled. If the Client ID is not in the right shape, MeetingHub warns: This should look like 3fa85f64-5717-4562-b3fc-2c963f66afa6.
Step 7: Authorise MeetingHub to connect Microsoft Teams to WordPress #
The keys tell MeetingHub which app to use. Now your Microsoft account has to say yes, once, so MeetingHub can create meetings on its calendar.
- On Authorise (Allow MeetingHub on your account), click Authorise with Microsoft Teams.

- Sign in with the Microsoft 365 account that will organize the meetings.
- Read the Permissions requested screen. You will see the app name you chose in Step 2 and the permissions from Step 4.
- Select Accept.
If Microsoft shows Need admin approval instead, your organization does not let users approve apps. Ask an administrator to grant admin consent on the app’s API permissions page (Step 4), then authorise again.
Microsoft sends you back to MeetingHub > Integrations, and the panel opens again on Ready.
Important: Only accept when the app name and account are the ones you set up.
Step 8: Confirm Microsoft Teams is connected to WordPress #
- If the panel is not on Ready already, click Ready at the top.
- Check that it reads Microsoft Teams is connected and New meetings and bookings can use it now.

From here you can:
- Click Create a meeting to schedule your first Teams meeting.
- Click Review meeting defaults to set the timezone, attendee camera, attendee microphone and automatic recording for every new Teams meeting.
- Click Disconnect to stop MeetingHub using your Microsoft account. Your keys stay saved.
Note: The Repeats, Require registration, Attendee camera, Attendee microphone and Record automatically defaults require MeetingHub Pro.
The Microsoft Teams card in Integrations now shows Connected.
What attendees see #
Each Teams meeting is a real event on your Microsoft 365 calendar, with a Teams join link. On your site, attendees see the meeting page with Join now, which opens Microsoft Teams, and View in calendar. When a meeting needs registration, they see Register now first.
Troubleshooting #
AADSTS50011: The redirect URI does not match #
Microsoft refused the sign-in because the redirect URI in your app registration is not the one MeetingHub sent.
Check that:
- You copied the URL with Copy in MeetingHub, not by hand.
- You added it under Authentication as a Web platform, not Single-page application.
https,wwwand the trailing slash match your site address exactly.
AADSTS50194: The app is not configured as a multi-tenant application #
The app registration is set to Single tenant only. Open the app’s Authentication page in the Microsoft Entra admin center, change Supported account types to Multiple Entra ID tenants, save, and authorise again.
“Sign-in did not finish. Check that the Client ID, Client Secret and Redirect URI in your app match the ones shown here, then try again.” #
Microsoft accepted your sign-in, but your site could not swap it for a token. The usual cause is the client secret.
Check that:
- Client secret holds the secret’s Value, not its Secret ID.
- The secret has not expired under Certificates & secrets.
- Client ID is the Application (client) ID of the same app.
Paste the right values, click Save keys, then Authorise with Microsoft Teams again. To send the details to support, click Copy details for support.
“Authorisation did not complete. Try again.” #
Microsoft returned an error, shown after The provider said:. If it says access_denied, someone clicked Cancel, or your organization needs an administrator to approve the app. Ask an administrator to select Grant admin consent on the app’s API permissions page, then try again.
“This sign-in link has expired. Please start the Microsoft Teams connection again.” #
The sign-in took too long, or the page was opened from an old link. Go back to the Microsoft Teams card in MeetingHub > Integrations and click Authorise with Microsoft Teams again.
“Sign-in needs https” or “Sign-in will fail with Plain permalinks” #
MeetingHub shows these warnings before you authorise. Microsoft refuses http addresses on real domains, and the return address needs pretty permalinks. Turn on HTTPS, or click Open Permalinks and pick any option other than Plain, then connect again.
The meeting page says “No join link available” #
The organizer account is a personal Microsoft account. Microsoft gives Teams links only to Microsoft 365 Business or Education accounts. Disconnect, then authorise again with a work or school account.
The sign-in still fails #
Open Tools > Site Health. MeetingHub checks your permalinks, https, server clock and whether your server can reach Microsoft, and Recent platform errors on the Info tab shows what Microsoft said. See How to check your MeetingHub setup with WordPress Site Health.
Frequently asked questions #
Do I need an Azure subscription? #
No, not with a Microsoft 365 work or school account. It already includes Microsoft Entra ID, where you register the app.
Can I use a personal Microsoft account? #
No, not for Teams links. A personal account can sign in, but Microsoft does not give it Teams meeting links. Use a Microsoft 365 Business or Education account.
Do I need the Tenant ID? #
No. You can leave Tenant ID empty.
What happens when the client secret expires? #
MeetingHub can no longer create Teams meetings. Add a new secret in Certificates & secrets, paste its Value into Client secret, click Save keys, and authorise again.
What happens to my meetings if I disconnect? #
They stay on your Microsoft 365 calendar and their join links keep working. You cannot create or change Teams meetings from MeetingHub until you reconnect.
Security best practices #
- Keep the client secret’s Value private. Never share it in screenshots, support tickets, email or code repositories.
- Choose a secret expiry you will remember, and set a reminder to replace it.
- Give WordPress administrator access only to people you trust. Only administrators can see and change these keys.
- Add only the permissions listed in Step 4.
- If the secret leaks, delete it under Certificates & secrets, create a new one, and paste its Value into MeetingHub.
- Delete the app registration if you stop using MeetingHub.
You’re ready to create Teams meetings #
Your site now talks to Microsoft Teams through your own app registration, and the permissions and secret stay in your own organization. Next, set your Teams defaults and create your first meeting.
- How to create your first online meeting in WordPress with MeetingHub
- How to set default meeting settings for each platform
- How to set up recurring meetings in WordPress
- How to create a booking page in WordPress with MeetingHub
- How to connect Zoom to WordPress with MeetingHub
- How to check your MeetingHub setup with WordPress Site Health