Getting a Dataverse for Teams Environment URL
When working with Microsoft Dataverse for Teams, there will be occasions where you’ll need to identify what the environment URL is. For example, if you need to escalate a problem to Microsoft or if you are looking to build out some data visualisation reports using Power BI Desktop. If you navigate into the Power Platform Admin Center and the settings pane for your environment, however, you will notice that the information is not visible within there:
Instead, we have to go into Microsoft Teams to get this information, as follows:
- Select the Power Apps app from the navigation bar:
- The Home tab should open in the main window. Select Build at the top:
- You should then see the list of all your Dataverse for Teams environments setup. First, select the one that you wish to get the URL for and then select the About tab (this order is essential 😉):
- When the About tab loads, click on the Session details option:
- The Environment URL will then be visible within the dialog that loads:
Quite a few steps are involved, as you can see. 😅 It’s perhaps understandable why Microsoft tuck this information away so carefully. Apart from the two occasions mentioned earlier, the need to refer to this bit of data will be limited. Don’t forget that most (if not all) other scenarios where this URL is vital, such as from an SDK standpoint, are restricted explicitly as part of Dataverse for Teams. You can consult this handy article on the Microsoft Docs site to find out more. Therefore, your only option to unlock additional capacity and force the Environment URL to become visible within the Power Platform Admin Center is to upgrade the environment/app into a proper Dataverse environment. But that’s a topic for another time maybe. 😄
Published on:
Learn moreRelated posts
Message Trace support on Graph API is now in Public Preview
Message Trace support on Microsoft Graph API is now in Public Preview, offering a modern REST-based experience for Exchange Online email traci...
Microsoft 365 Copilot: Custom dictionary expands language support and increases limits for Teams meeting transcripts
Microsoft 365 Copilot’s custom dictionary now supports more languages, doubles per-language entry limits to 1,000, and allows incremental CSV ...
Microsoft 365 Copilot: AI audio overview support for pages and additional languages in Viva Connections and SharePoint
Microsoft 365 Copilot is expanding AI audio overview support in Viva Connections and SharePoint, adding more languages and AI-generated audio ...
Teams Revamps Premium Licensing
Microsoft announced a set of Teams licensing changes to take effect in April 2026. The changes affect devices, Microsoft Places, and Teams eve...
Fetch message trace data via the Graph API
A quick look at the recently introduced /admin/exchange/tracing/messageTraces Graph API endpoint to fetch Exchange Online message trace detail...
Turn Chaos into Clarity: Build a Simple Risk & Issue Register with Teams + Copilot
In yesterday’s blog, I looked at how Microsoft Teams can become the central hub for managing your project, conversations, meetings, tasks, and...
SharePoint Embedded – Your first steps
As the SharePoint Embedded connector was released last night, I thought it would be useful to start a series of posts about SharePoint Embedde...
Still no good solution for cleaning deleted items via the Graph API
2026 is the year in which Microsoft plans to pull the plug on EWS, and before this happens, I’m taking some time to go over my code samp...
Microsoft Teams: Digital signage in Teams Rooms on Android
As with Teams Rooms on Windows, IT Admins can now set up Teams Rooms on Android to show dynamic signage content on the front-of-room display w...