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
Microsoft Dynamics 365 vs Salesforce: A Practical Comparison for Enterprise Teams
In many organizations currently using Salesforce, the friction does not initially feel like a CRM problem. It feels like extra steps throughou...
Restricting Access is The Most Important Step in a Microsoft 365 Copilot Deployment
I was asked what the most important step is in the deployment of Microsoft 365 Copilot. It's a good question. Put simply, restricted access is...
Microsoft 365 Copilot in Word: Improved support for complex edits
Microsoft 365 Copilot in Word will support complex edits like tracked changes, comments, and document structure while preserving formatting an...
Copilot Notebooks available in Microsoft 365 Copilot Chat for Basic users
Copilot Notebooks will be available in Microsoft 365 Copilot Chat for Basic users starting mid-June 2026, providing a persistent AI-powered wo...
Rolling out a simplified, consistent design and navigation experience in Viva Engage
Viva Engage is updating to a simplified, consistent design and navigation across web and Teams, improving usability and reducing clutter. The ...
Microsoft 365 Copilot: Retirement of Sora video generation experience (Frontier)
The Sora video generation experience in the Frontier program will retire between mid and late June 2026. Users will lose access to create new ...
Microsoft 365 & Power Platform Call (Microsoft Speakers) – June 9th, 2026 – Screenshot Summary
Call Highlights  SharePoint Quicklinks: Primary PnP Website: https://aka.ms/m365pnp Documentation & Guidance SharePoint Dev Videos Issues...