Shared Calling Setup Microsoft Teams

To assign an emergency location to a user in Microsoft Teams using PowerShell, you need to ensure that you have the necessary permissions to execute the command. The "Access Denied" error typically indicates that your account does not have the required permissions to perform this action.

Here are some steps you can take to resolve the issue:

1. Check Permissions: Ensure that your account has the appropriate role assigned in Microsoft Teams. You may need to be a Teams Administrator or have a similar role that allows you to manage phone numbers and emergency locations.
2. Use the Correct Command: The command you are using seems to be missing the -LocationId parameter. The correct command should look like this:

      Set-CsPhoneNumberAssignment -Identity ******@rentoakharbor.com -PhoneNumber +13606728800 -PhoneNumberType CallingPlan -LocationId 'bfa753b7-9dad-4a69-a4e3-a30973fc2146'
   

3. Run PowerShell as Administrator: Make sure you are running PowerShell with administrative privileges. Right-click on the PowerShell icon and select "Run as administrator".
4. Contact Your Administrator: If you are still encountering issues, it may be necessary to contact your IT administrator to verify your permissions or to perform the assignment on your behalf.
5. Review Documentation: For more detailed instructions on assigning phone numbers and emergency locations, refer to the official Microsoft documentation on using PowerShell for Teams.

By ensuring you have the right permissions and using the correct command syntax, you should be able to successfully assign the emergency location to the user.

References:

• Use PowerShell to assign a phone number to a user
• Configure Shared Calling

Dear @BW - Oak Harbor Property Management,
Thank you for posting your question in the Microsoft Q&A forum. I understand you’ve tried assigning an emergency location to your Teams Resource Account using PowerShell, but you continue to receive an “Access Denied” error despite following all recommended steps.

Since you confirmed that permissions, correct command syntax, running PowerShell as administrator, and reviewing documentation did not resolve the issue and you are the IT administrator which indicates the problem is not on your side.

This error typically occurs when there is a backend provisioning or policy enforcement issue within Microsoft 365 services. Even if all prerequisites (roles, licenses, emergency location setup, usage location) are correct, the assignment can fail due to tenant-level configuration or replication delays.

So I recommend you raise support ticket from Microsoft Admin Center.

• Create a support ticket: from Microsoft 365 admin center> Support > New Service Request. Admin can raise support ticket from https://admin.microsoft.com/#/support/requests
• Submit a Service Request: The Global Admin should create a service request with Microsoft support to get advanced technical assistance and diagnostics. For detailed instructions on how to get support, please refer to Get support - Microsoft 365 admin.

A technical support engineer will help you through a remote session to investigate the situation, verify the backend configurations, and run any necessary synchronization tools to resolve the problem. If the issue requires further attention, they can escalate it to a specialized team for deeper analysis.

I truly appreciate your patience and understanding. If you have any further questions or need further clarification, please feel free to reach out. I'm looking forward to hearing from you. 

Thank you for your cooperation.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.