Description
This article fixes Teams Rooms accounts that have a valid Teams Rooms Basic or Teams Rooms Pro licence but are refused by Teams as unlicensed. The fix is a single tenant setting in the Microsoft 365 admin centre.
Symptoms:
- The Teams Rooms device (for example a Yealink MeetingBar) shows: "Sign-in error. Your license doesn't include access to Microsoft Teams. Ask your IT administrator for access."
- Signing in to teams.microsoft.com as the room account shows: "You don't have the required permissions to access this org."
- Every Teams Rooms account in the tenant is affected, including brand-new accounts that have only ever had a Teams Rooms licence.
- The same account works if it's given a Microsoft 365 Business or Enterprise licence instead.
Everything else checks out. The licence is assigned with all apps enabled, Get-CsOnlineUser shows the Teams feature types, the Remote Connectivity Analyzer Teams Rooms sign-in test passes its licence checks, and Entra sign-in logs show Teams tokens being issued successfully.
Cause: the Microsoft 365 admin centre still holds a legacy tenant-level setting that turns Teams on or off by licence type. Teams Rooms Basic and Pro fall under the Other licence type. If Other isn't ticked, Teams refuses every account that relies on a Teams Rooms licence. Microsoft hasn't documented why this would be unticked in a tenant, but it's been reported before when the Teams Rooms Basic and Pro licences were introduced (Microsoft Q&A).
Requirements
- A Global Administrator login for the customer's Microsoft 365 tenant
- The Teams Rooms resource accounts, each with a Teams Rooms Basic or Teams Rooms Pro licence assigned
- A web browser with a private or incognito window, to test the room accounts
- Physical or remote access to the Teams Rooms devices, to sign them in once the fix is in place
The Process
Before you start: don't try to work around this by assigning a Business or Enterprise licence, swapping licences back and forth, or deleting and recreating the room accounts. These can get a room signed in temporarily, which hides the real cause until the device re-checks its licence and drops out again. Every change also restarts licence provisioning, adding delay. Fix the setting below first.
- Confirm the licence is assigned correctly.
- In the Microsoft 365 admin centre (admin.microsoft.com), go to Users > Active users and select a room account.
- Open Licenses and apps. Check that Microsoft Teams Rooms Basic or Pro is ticked and that Microsoft Teams is ticked under Apps.
- If the licence or the Teams app is missing, fix that first. This article only applies when the licence is in place.
- Open the Teams licence type setting.
- Signed in as a Global Administrator, go to Settings > Org settings.
- On the Services tab, select Microsoft Teams.
- Enable the Other licence type.
- In the panel, review the licence types Teams is turned on for.
- Tick Other. This covers Teams Rooms Basic and Teams Rooms Pro.
- Leave the other licence types as they are, unless the customer also wants guest access to Teams, in which case tick Guest too.
- Click Save.
- Wait for the change to apply. It can apply within about 20 minutes, but allow up to a few hours before treating it as failed.
- Test a room account in a browser.
- Open a private or incognito window and go to teams.microsoft.com.
- Sign in as the room account. Teams should load instead of the "You don't have the required permissions" error.
- Sign in the Teams Rooms devices.
- Sign each device in as its room account, the same way as during setup.
- If a device still shows the licence error after the browser test works, restart it and try again. If it still fails, factory reset the device and sign in fresh, as Android Teams Rooms devices cache the earlier licence state.
- Remove any workarounds.
- Remove any Microsoft 365 Business or Enterprise licences added to room accounts while troubleshooting. These aren't permitted on shared meeting devices.
- Cancel any temporary Teams Rooms Pro licences and delete any test accounts created along the way.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article