Purview-Databricks Integration API version 2023-10-01-preview. Unable to scope scan to schema-level

Question

Purview-Databricks Integration API version 2023-10-01-preview. Unable to scope scan to schema-level

Thomas, Anna (External) 40

We are currently using this Purview-Databricks Integration API version 2023-10-01-preview to scope the scan to schema-level but its throwing this error: User's image

Please help.

Chandra Boorla 15,475 Reputation points Microsoft External Staff Moderator

2025-07-25T02:05:31.51+00:00
Hi Thomas, Anna (External)

The error message you're seeing - Error: (3818) Connector Exception: Value cannot be null. (Parameter 'metastoreId') indicates that the metastoreId parameter is missing or set to null when configuring a schema-level scan using the 2023-10-01-preview version of the Purview-Databricks Integration API.

In this preview version, schema-level scans require the Unity Catalog metastoreId to be explicitly provided, as it identifies which metastore to scan.

Resolution:

Please ensure that you're passing the correct metastoreId in your scan configuration. For example, your API request should include something like:

{ "scanLevel": "Schema", "metastoreId": "<your-unity-catalog-metastore-id>", ... }

How to find your metastoreId:

Go to your Azure Databricks workspace --> Navigate to the Unity Catalog settings --> Locate and copy the Metastore ID.

Alternatively, you can call the Unity Catalog API:

GET /api/2.1/unity-catalog/metastores

Once you include the correct metastoreId, your schema-level scan should proceed successfully.

For more details, please refer: Connect to and manage Azure Databricks Unity Catalog in Microsoft Purview

I hope this information helps. Please do let us know if you have any further queries.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

As your feedback is valuable and can assist others in the community facing similar issues.

Thank you.
Smaran Thoomu 35,205 Reputation points Microsoft External Staff Moderator

2025-07-25T18:50:35.7033333+00:00

Thomas, Anna (External) We received your feedback that the answer provided on the thread was not helpful.

Kindly let us know what we could have done better to improve the answer and make your engagement experience good. We are here to help you and strive to make your experience better and greatly value your feedback.

Our engineer have provided a detailed answer which has clear steps for which you are looking for. If you wish, you may re-surveying/rating for the engagement you received on the thread. Your feedback is very important to us.

Looking forward to you reply. Much appreciate your feedback!
Thomas, Anna (External) 40 Reputation points

2025-07-25T22:17:13.0833333+00:00

We already had MetastoreID defined (per the answer) when using this version of the API. So the recommendation solution was not helpful. What we ended up doing is falling back to the older version of the API and that ended up working for us.

Answer accepted by question author

0 additional answers

Your answer

Chandra Boorla 15,475 Reputation points Microsoft External Staff Moderator

2025-07-25T02:05:31.51+00:00

Hi Thomas, Anna (External)

The error message you're seeing - Error: (3818) Connector Exception: Value cannot be null. (Parameter 'metastoreId') indicates that the metastoreId parameter is missing or set to null when configuring a schema-level scan using the 2023-10-01-preview version of the Purview-Databricks Integration API.

In this preview version, schema-level scans require the Unity Catalog metastoreId to be explicitly provided, as it identifies which metastore to scan.

Resolution:

Please ensure that you're passing the correct metastoreId in your scan configuration. For example, your API request should include something like:

{ "scanLevel": "Schema", "metastoreId": "<your-unity-catalog-metastore-id>", ... }

How to find your metastoreId:

Go to your Azure Databricks workspace --> Navigate to the Unity Catalog settings --> Locate and copy the Metastore ID.

Alternatively, you can call the Unity Catalog API:

GET /api/2.1/unity-catalog/metastores

Once you include the correct metastoreId, your schema-level scan should proceed successfully.

For more details, please refer: Connect to and manage Azure Databricks Unity Catalog in Microsoft Purview

I hope this information helps. Please do let us know if you have any further queries.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

As your feedback is valuable and can assist others in the community facing similar issues.

Thank you.
Smaran Thoomu 35,205 Reputation points Microsoft External Staff Moderator

2025-07-25T18:50:35.7033333+00:00

Thomas, Anna (External) We received your feedback that the answer provided on the thread was not helpful.

Kindly let us know what we could have done better to improve the answer and make your engagement experience good. We are here to help you and strive to make your experience better and greatly value your feedback.

Our engineer have provided a detailed answer which has clear steps for which you are looking for. If you wish, you may re-surveying/rating for the engagement you received on the thread. Your feedback is very important to us.

Looking forward to you reply. Much appreciate your feedback!
Thomas, Anna (External) 40 Reputation points

2025-07-25T22:17:13.0833333+00:00

We already had MetastoreID defined (per the answer) when using this version of the API. So the recommendation solution was not helpful. What we ended up doing is falling back to the older version of the API and that ended up working for us.

Answer 1

Thomas, Anna (External)

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer.

Issue:

We are currently using this Purview-Databricks Integration API version 2023-10-01-preview to scope the scan to schema-level but its throwing this error: User's image

Solution:

We had already included the metastoreId in our configuration when using the 2023-10-01-preview API version, so the suggested solution didn’t resolve the issue. Ultimately, we reverted to the older API version, which worked as expected.

If I missed anything please let me know and I'd be happy to add it to my answer, or feel free to comment below with any additional information.

Hope this helps. Do let us know if you have any further queries.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Share via

Purview-Databricks Integration API version 2023-10-01-preview. Unable to scope scan to schema-level

0 additional answers

Your answer