Here’s a handy list of URLS Teams Handsets access.
This list was captured using a Pi-hole, from the moment the handset was turned on, registering with Intune and Azure AD, and signing in to Teams. Making calls and joining a meeting are also included.
Note: The list only includes URLs and does not include IP addresses that are listed here: Office 365 URLs and IP address ranges – Microsoft 365 Enterprise | Microsoft Docs
| A | 0.pool.ntp.org |
| SRV | _ntp._udp.time.windows.com |
| A | a.manage.microsoft.com |
| A | aadcdn.msauth.net |
| A | aadcdn.msftauth.net |
| A | android.clients.google.com |
| A | api.flightproxy.teams.microsoft.com |
| A | api.microsoftstream.com |
| A | api3.cc.skype.com |
| A | au.ng.msg.teams.microsoft.com |
| A | auea-1.api.microsoftstream.com |
| A | authsvc.teams.microsoft.com |
| A | authsvc.teams.microsoft.com |
| A | config.teams.microsoft.com |
| A | connectivitycheck.android.com |
| A | devicemgmt-cdn.teams.microsoft.com |
| A | devicemgmt.teams.microsoft.com |
| A | enterpriseregistration.windows.net |
| A | fef.msud01.manage.microsoft.com |
| A | firebaseinstallations.googleapis.com |
| A | firebaseremoteconfig.googleapis.com |
| A | go.microsoft.com |
| A | go.trouter.teams.microsoft.com |
| A | graph.microsoft.com |
| A | graph.windows.net |
| A | ic3.events.data.microsoft.com |
| A | in.appcenter.ms |
| AAAA | ipv4only.arpa |
| A | japanwest-prod.notifications.teams.microsoft.com |
| A | login.live.com |
| A | login.microsoftonline.com |
| A | mamservice.manage.microsoft.com |
| A | mobile.pipe.aria.microsoft.com |
| A | mtalk.google.com |
| A | odc.officeapps.live.com |
| A | outlook.office.com |
| A | presence.teams.microsoft.com |
| A | teams.microsoft.com |
| A | time.windows.com |
| A | whiteboard.microsoft.com |
| A | worldaz.relay.teams.microsoft.com |
| AAAA | trouter2-azsc-auea-0-a.trouter.teams.microsoft.com |
| A | auc.pptservicescast.officeapps.live.com |
why would these be any different from a Teams soft client (excepting the Intune management requirements may differ)
Teams has its own device management (devicemgmt.teams.microsoft.com) for updates, config, and remote actions (reboots etc)
yup – that URL is where firmware updates come from for Android-based devices.
the google URL’s mentioned above, do these need to be allowed for Teams Phone devices to function? In our environment, I believe they are blocked. However we are seeing random phones signing out, and dial tone and outgoing calls seem to fail after a phone has been sitting idle for a while, then on second attempt it seems to work.
No, these aren’t 100% required for the phone to function.