ADME Technical Reference
Factual reference for Equinor's Azure Data Manager for Energy (ADME) deployment.
Instances
| Environment | Instance | Data Partition | Base URL |
|---|---|---|---|
| Development | equinorswedev | dev |
https://equinorswedev.energy.azure.com |
| Test | equinorswetest | test |
https://equinorswetest.energy.azure.com |
| Production | equinorswe | data |
https://equinorswe.energy.azure.com |
Each instance is a complete, independent OSDU deployment with its own data, entitlements, and services. See Configuration Files for ready-made configs per environment.
For the full list of service endpoints, paths, and Swagger docs, see OSDU APIs.
Authentication
All access to ADME goes through Microsoft Entra ID using OAuth2.
- Your client app requests an access token from Entra ID
- Entra ID returns the token
- Your app sends the API request to ADME with the token attached
Without a valid token, the request is rejected at the security barrier. For a conceptual overview of how authentication works, see ADME — Authentication.
OSDU vs ADME
| OSDU | ADME | |
|---|---|---|
| What | Open standard and API specification | Microsoft's hosted implementation |
| Who runs it | Defined by The Open Group | Operated by Microsoft on Azure |
| APIs | Standard OSDU APIs | Same APIs, hosted on Azure endpoints |
| Identity | Supports multiple identity providers | Uses Microsoft Entra (AAD) |
To understand the relationship between OSDU and ADME, see ADME — How ADME relates to OSDU.
External links
See also
- ADME (concept) — what ADME is and why Equinor uses it
Last update:
2026-03-24