Dataverse environmentid vs organizationid

Coming from a Dynamics CRM background, I mainly used the organizationid in the past (the organizationid is the unique identifier associated to a CRM instance). So having to use both organizationids and enviromentids isn't always easy,  and sometimes I still mix the two  - readability isn't a trait of GUIDS ... 

First some background on why we have two identifiers. With the July 2018 update of Dynamics CRM (version 9.0) Microsoft separated out the core platform features and the various business modules (Sales, Customer Service, etc...)  and this was also the point in time where CRM consultants where suddenly faced with a second identifier for a Dynamics CRM instance - the environmentid.

To find both the environmentid and organizationid of an instance, you open up the maker portal and select the developer resources link in the settings menu for an instance.

From this page you can find both the environmentid and organizationid - the Microsoft documentation still points to the legacy interface - Determine your environment's organization ID and name which starting from the maker portal requires quite a few additional steps ...

You will need to use the environmentid when working with the Power Platform Admin PowerShell cmdlets, Power Platform for Admins Cloud flow connector as well as the Power Platform API

References:

• Making sense of XRM, PowerApps and some other acronyms (CDS,CDM, ...)