After you change a user’s Microsoft 365 license, Teams may stop detecting the emergency location for that user. This usually happens when the license change removes or alters the Teams Phone System or Calling Plan capabilities. The emergency location is tied to the user’s assigned phone number and the policy that maps that number to … Read more
Your Teams Rooms Android device is not showing the emergency location, so 911 calls may lack the correct address. This problem usually happens because the device has no location permission, the network blocks location services, or the Teams Rooms app is outdated. This article explains the root cause and gives step-by-step fixes to make the … Read more
Your remote user dials 911 in Teams, but the call routes without a registered emergency address. The dispatcher cannot identify the caller’s location, which delays help. This failure usually happens because the user’s network connection does not match the emergency location policy you assigned. This article explains why Teams fails to detect the location and … Read more
If Teams cannot detect your emergency location after a network firewall change, your calls to 911 or local emergency services may route to the wrong dispatch center. This problem usually appears when the firewall blocks the specific endpoints Teams uses for location discovery. This article explains why the firewall blocks location detection, how to verify … Read more
When you open the Teams admin center to assign an emergency location, the location list may appear empty or show a “Not detected” error. This blocks you from assigning a location to a user or to a network identifier. The problem usually comes from a missing or misconfigured network zone, a location that was created … Read more
Your Teams call queue suddenly stops ringing after your network team updates the firewall. Calls go straight to voicemail or fail with a busy tone. The root cause is almost always a blocked or misdirected connection to Microsoft 365 services. This article explains the exact ports and endpoints the call queue needs and gives you … Read more
When a Teams call queue stops ringing, callers hear a busy tone or get disconnected. This issue typically appears after a policy change or a resource account misconfiguration. The problem often stems from the call queue’s routing settings, agent assignment, or the associated resource account being unlicensed. This article explains the root causes and provides … Read more
Your Teams auto attendant suddenly routes calls to the wrong queue or user after a license change. This typically happens when the licensed user assigned to the auto attendant loses a required Teams Phone license, or when the resource account is reassigned. The auto attendant itself relies on resource accounts and licensed call agents to … Read more
When a Teams Rooms Android device receives a call, the auto attendant may route it to the wrong destination. You expect the call to ring the front desk, but it lands on a personal voicemail or a different queue. This usually happens because the device is assigned to the wrong resource account, the auto attendant … Read more
When a remote user dials your organization’s main number, the Teams auto attendant should route them to the correct department or person. Instead, calls may land on a hunt group, a shared voicemail, or the operator. This happens because the auto attendant’s routing logic relies on the caller’s phone number, not their Teams profile. This … Read more