Platform FAQ
Common questions about the OSDU Data Platform at Equinor.
What is the difference between OSDU and ADME?
OSDU is the open standard for subsurface data management. ADME (Azure Data Manager for Energy) is Microsoft's managed deployment of that standard. At Equinor, ADME is the actual infrastructure running the OSDU Data Platform. See What is OSDU? and ADME.
What environments are available?
There are three: Development, Test, and Production. The intended use of each environment is to be determined. All Equinor employees have read access to Development and Test by default. See ADME Technical Reference for URLs and partition IDs.
How do I authenticate my application?
Register an app in Entra ID, then use the OSDU Python SDK with OsduMsalNonInteractiveCredential for non-interactive access. See App Registration and Connecting to an Environment.
How does Entra ID work with OSDU?
All authentication to the OSDU Data Platform goes through Microsoft Entra ID. Users authenticate interactively, and applications use client credentials to obtain tokens. Entra ID also controls which security groups map to OSDU entitlement groups. See Entra ID Integration.
How do I search for data?
Use the Search API via CLI, Python SDK, or raw HTTP. You can filter by kind, query metadata fields, and paginate results. See Searching for Data.
Where do I find API endpoints and Swagger docs?
All service endpoints, health checks, and Swagger links are listed in API Reference. Swagger docs are also available directly on each environment at https://{instance}/api/{service}/swagger-ui.html.
My search returns no results but I know the data exists — what's wrong?
This is usually an indexing issue. Records exist in Storage but haven't been indexed by the Search service yet. See Troubleshooting Indexing Errors.
Where can I find ready-made configuration files?
Connection configs for each environment (Development, Test, Production) are available at Configuration Files.