Fix Teams Call Queue Does Not Ring after a License Change
🔍 WiseChecker

Fix Teams Call Queue Does Not Ring after a License Change

Your Teams call queue stops ringing after you change a user’s license. The queue still exists in the Teams admin center, but incoming calls go straight to voicemail or disconnect. This usually happens because the license change removed the phone system or calling plan capabilities that the call queue relies on. This article explains why the license change breaks the call queue and gives you the exact steps to restore ringing.

Key Takeaways: Restore Call Queue Ringing After License Changes

  • Teams admin center > Voice > Call queues: Check the resource account and licensing status for each call queue.
  • Microsoft 365 admin center > Users > Active users > Licenses: Reassign the Phone System and Microsoft Teams Calling Plan licenses to the resource account.
  • PowerShell cmdlet Get-CsOnlineUser: Verify that the resource account has the correct EnterpriseVoiceEnabled and HostedVoiceMail settings.

ADVERTISEMENT

Why a License Change Silences Your Call Queue

A Teams call queue is not a standalone object. It depends on a resource account that holds the phone number and the licensing that enables calling. When you change a user’s license, you might accidentally remove the Phone System license from the resource account that the call queue uses. Without that license, the resource account cannot route calls, so the queue stops ringing.

The same issue occurs if you remove a Microsoft Teams Calling Plan license. The calling plan provides the minutes for domestic or international calls. Without it, the call queue cannot connect to external phone numbers. Even if the Phone System license remains, the call fails because there is no calling plan.

Another common cause is that the license change removes the resource account from the call queue’s agent list. When you edit a user’s licenses, Teams may reset the account’s service number or reassign it. The call queue then points to an unlicensed or invalid resource account, so it stops ringing.

Understanding these dependencies helps you fix the issue quickly. You need to verify three things: the resource account’s licenses, the call queue’s assignment, and the phone number’s availability.

Steps to Diagnose and Fix the Call Queue After a License Change

Follow these steps in order. Each step checks a different part of the call queue configuration.

Step 1: Verify the Resource Account Licenses

  1. Open the Microsoft 365 admin center
    Go to admin.microsoft.com and sign in with an account that has Global Administrator or User Administrator permissions.
  2. Find the resource account
    Select Users > Active users. Search for the resource account name. Resource accounts usually have a name like “CallQueue-Resource” or “AutoAttendant-Resource”.
  3. Check the license assignments
    Click the user, then select Licenses and apps. Confirm that the following licenses are assigned: Phone System and Microsoft Teams Calling Plan. If either is missing, click Edit, check the boxes, and save.
  4. Verify the calling plan
    Under the Microsoft Teams Calling Plan license, confirm that a calling plan is selected, such as Domestic Calling Plan or International Calling Plan. If no plan is selected, the license is present but useless.

Step 2: Confirm the Call Queue Still Points to the Resource Account

  1. Open the Teams admin center
    Go to admin.teams.microsoft.com and sign in with the same admin account.
  2. Navigate to the call queue
    Select Voice > Call queues. Find the call queue that is not ringing and click its name.
  3. Review the resource account
    Look at the Resource account section. Confirm that the correct resource account is selected. If the field is empty, click Edit, choose the resource account, and save.
  4. Check the phone number
    In the same page, verify that the resource account has a phone number assigned. If the number is missing, assign the original number or a new one under the resource account’s Voice settings.

Step 3: Use PowerShell to Validate the Configuration

  1. Install the Teams PowerShell module
    Open Windows PowerShell as an administrator and run: Install-Module -Name MicrosoftTeams -Force. If you already have it, skip this step.
  2. Connect to Teams
    Run Connect-MicrosoftTeams and sign in with the admin account.
  3. Check the resource account
    Run Get-CsOnlineUser -Identity “resourceaccount@domain.com” | Select EnterpriseVoiceEnabled, HostedVoiceMail, OnlineVoiceRoutingPolicy. If EnterpriseVoiceEnabled is False, the resource account lacks the Phone System license.
  4. Fix the enterprise voice setting
    If EnterpriseVoiceEnabled is False, assign the Phone System license in the Microsoft 365 admin center, then run Set-CsUser -Identity “resourceaccount@domain.com” -EnterpriseVoiceEnabled $true.

Step 4: Reassign the Phone Number if Needed

  1. Open the Teams admin center
    Go to Voice > Phone numbers.
  2. Locate the resource account’s number
    Find the phone number that was assigned to the resource account. Check its Assignment status. If it shows Unassigned, click the number, then select Assign.
  3. Assign to the resource account
    In the Assign dialog, choose Voice user or Resource account, select the resource account, and save.
  4. Test the call queue
    Call the queue’s number from a mobile phone. If it rings, the fix is complete.

ADVERTISEMENT

If the Call Queue Still Does Not Ring After the Main Fix

Sometimes the license change causes secondary issues. Check the following scenarios if the queue remains silent.

Call Queue Shows “No Agents” After the License Change

The license change might have removed all agents from the queue. Go to the call queue’s settings and verify the Agent assignment list. If it is empty, add the users again. Also confirm that each agent has the Phone System license assigned.

Resource Account Is Disabled or Deleted

A license change can accidentally disable the resource account. In the Microsoft 365 admin center, check the account’s Sign-in status. If it is blocked, click the user and select Unblock sign-in. Then verify the account is licensed.

Calls Go to Voicemail Instead of Ringing

This happens when the call queue’s routing method is set to Voicemail or when the resource account has a voicemail policy. Open the call queue and check the Call answering section. Set it to Route calls to agents. Also remove any voicemail policy from the resource account using PowerShell: Set-CsUser -Identity “resourceaccount@domain.com” -HostedVoiceMail $false.

Call Queue Licensing Options: Phone System Only vs Phone System with Calling Plan

Item Phone System Only Phone System with Calling Plan
Required license Microsoft 365 Phone System Microsoft 365 Phone System + Teams Calling Plan
Can receive external calls Yes, if you use Direct Routing Yes, directly via Microsoft
Call queue works without calling plan Yes, only for internal calls Yes, for all calls
Typical setup Used with third-party telephony Used with Microsoft as the carrier

Now you can restore the call queue by checking the resource account licenses, reassigning the phone number, and verifying the configuration with PowerShell. After the fix, test the queue with a real call. To prevent this issue in the future, always check the resource account’s licenses before you change any user’s licensing. Use the Teams admin center’s Call queue report to monitor the queue’s health weekly.

ADVERTISEMENT