1,652 questions
About the vCore across all scans of Microsoft Purview Data Map Automated Scanning.
Phakphoom Claiboon
0
Reputation points
Hi,
I want to estimate the pricing of Microsoft Purview as following Azure Pricing calculator (https://azure.microsoft.com/en-au/pricing/calculator/).
I did not understand at some point and need to find an explanation about this. you can see my questions below:
- Where does the default value 32 vCores of vCores across all scans of Microsoft Purview Data Map Automated Scanning in Azure Pricing calculator come from?
- How to estimate Total vCores across all scans of Microsoft Purview Data Map?
- What's the performance of 1 vCores for scans of Microsoft Purview Data Map Automated Scanning?
Microsoft Security | Microsoft Purview
{count} votes
-
PRADEEPCHEEKATLA 90,736 Reputation points Moderator2023-12-01T05:46:03.5933333+00:00 @Phakphoom Claiboon - Thanks for the question and using MS Q&A platform.
The default value of 32 vCores for Microsoft Purview Data Map Automated Scanning in the Azure Pricing calculator is based on the default limit of 160 vCores available for scanning per account, as mentioned in the Microsoft Purview limits table in the Manage resources and quotas document. This means that if you have multiple accounts, the total vCores available for scanning across all accounts will be 160 multiplied by the number of accounts you have.
To estimate the total vCores across all scans of Microsoft Purview Data Map, you need to determine the number of accounts you have and multiply it by the number of vCores available for scanning per account. For example, if you have 2 accounts, the total vCores available for scanning across all accounts will be 160 x 2 = 320 vCores.
The performance of 1 vCore for scans of Microsoft Purview Data Map Automated Scanning depends on various factors such as the size and complexity of the data being scanned, the number of concurrent scans, and the type of data sources being scanned. Therefore, it is difficult to provide a specific performance metric for 1 vCore. However, you can refer to the Microsoft Purview limits table in the Manage resources and quotas document to understand the default limits and maximum limits for various resources, including vCores available for scanning per account.
For more details, refer to Microsoft Purview Pricing and introduction of Purview Applications.
I hope this helps! Let me know if you have any further questions.
-
Phakphoom Claiboon 0 Reputation points
2023-12-01T06:43:34.6433333+00:00 Thank you for your reply.
I have an additional question that is "Why use 32 vCores for the default value of vCores across all scans of Microsoft Purview Data Map Automated Scanning following Azure Pricing calculator?"
From your answer, the maximum total vCores across all scans is (vCores available for scanning, per account x Concurrent scans per Purview account) = 160 x 5 = 800 vCores
And incidentally that (vCores available for scanning, per account / Concurrent scans per Purview account) = 160 / 5 = 32 vCores which doesn't make sense and is not correct.
Then please explain why do you use the 32 vCores for the default value.
-
PRADEEPCHEEKATLA 90,736 Reputation points Moderator
2023-12-05T04:18:47.5533333+00:00 @Phakphoom Claiboon - This article highlights the limits that currently exist in the Microsoft Purview service.
-
PRADEEPCHEEKATLA 90,736 Reputation points Moderator
2023-12-13T02:49:51.5066667+00:00 @Phakphoom Claiboon - We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Sign in to comment
Sign in to answer