Rest API: Does the MS Purview have the same API fetch and call as Azure Purview?

Question

Currently in our Azure Purview environment we are using REST API to POST table descriptions, data type changes and column descriptions within the assets. These assets are scanned from on pre databases like Oracle. Does the new MS Purview follow the same endpoints and the payload as Azure Purview with regards to API or are there any changes to the API documentation?

Answer 1

I think that new purview still uses atlas, but the perms + routeing shifted and old calls miss. if u check the live typedefs first, the env drift shows up. wish this help

Answer 2

The Microsoft Purview REST API does have similarities with the Azure Purview API, particularly in how you create and manage assets. However, there are specific endpoints and payload structures that may differ depending on whether you are using the classic Microsoft Purview experience or the new Microsoft Purview portal.

For example, both experiences use the endpoint for creating entities, but the request URLs are different:

• Classic governance portal: https://{accountName}.purview.azure.com/catalog/api/atlas/v2/entity
• New Microsoft Purview portal: https://api.purview-service.microsoft.com/catalog/api/atlas/v2/entity

When working with the APIs, it is important to refer to the specific documentation for the version of Microsoft Purview you are using to ensure you are following the correct guidelines for endpoints and payloads.

You can find more detailed information about using the REST API for Microsoft Purview in the documentation.