Please enhance the lab with an example of Workflow and Approval

• Include a sample script for partners/customers looking to provision a batch of lab environments.

• Deploy to Azure should deploy a SQL VM resource and assign appropriate permissions to the user to log in and complete the lab walkthrough.

Add business scenarios/case study – e.g. this may be a separate module or PowerPoint slide.

• Update content within module (including screenshots).
• Build out REST API content for further learning around the topic.
• Update the REST API module to include the web-based version of Postman as a workaround.

@tayganr

Module 2a - having issues with using Storage Explorer on desktop - look at using AzCopy or other alternatives rather than desktop experience for people with issues using this

Possibility of including a Purview + MDM module /demo since I am seeing a lot of questions on this topic. Not sure how feasible it is given the 3rd party MDM element i.e. Profisee or other

1. In Module 5>task 6, step 3, the UI got updated for Azure Purview and we couldn't able to see the Schema option after selecting twitter_handles.parquet file. Please find the below screenshot for your reference.

2. In Module 7>task 5, the sensitivity label insights(preview) is not getting loaded inside the Sensitivity Labels section of Azure Purview as shown in the below screenshot.

3. In Module 9>task 3 after selecting twitter_handles.parquet file, facing an error "Invalid Parquet file size" as shown below while running the SQL query in synape workspace.

Mark Modules 1 to 9 as mandatory/minimum completion.

• Update content within module (including screenshots).

• Update content within module (including screenshots).

Extend SHIR module to cover scanning of on-premises SQL Server.

Knowledge Checks

• Update to include new self-rating against new modules (e.g. SHIR)
• Include an option for people to not self-rate if did not complete (e.g. bonus modules).

• Walkthrough the set-up of SHIR in the SQL VM and connection with Azure Purview.

(e.g. Best Practices)

• Update the pre-requisites to include:

  • Azure Fundamentals
  • Introduction to Azure Purview
  • Tools (Storage Explorer, Postman)

• Add references to the Elastic Data Map in Module 01.
• Include a question on the Elastic Data Map as part of the Knowledge Check.

• Update content within module (including screenshots).

• This step in the lab has been automated by the deploy to Azure scripts.
• Will only require deleting from each module.

• Update content within module (including screenshots).

Hi,
there seems to be an issue with authentification. After login with az login or VS Code I get:
DefaultAzureCredential failed to retrieve a token from the included credentials.
Attempted credentials:
EnvironmentCredential: EnvironmentCredential authentication unavailable. Environment variables are not fully configured.

Other azure cli commands seem to work

Christoph

• Update content within module (including screenshots).

Looks like the Keyvault Portal screens have moved on and the dialogue for this section (Module 02B - Register & Scan (Azure SQL DB)) doesn't quite match the current portal

I ended up with the error above which I think I fixed using this fix (https://jd-bots.com/2021/07/27/fixed-the-operation-list-is-not-enabled-in-this-key-vaults-access-policy/) but not sure if that's the right approach

The Objectives section of Module 12 and Module13 has the same text from "Module 11", which is "Connect to on premise data source using a self-hosted integration runtime.".

I believe the Objectives should be reviewed to better match the learning objectives of each module.

Just getting started with Microsoft Purview and encountered this error with a new set up.

{"code":"InvalidTemplateDeployment","details":[{"code":"QuotaExceeded","message":"Operation could not be completed as it results in exceeding approved standardDADSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: westus2, Current Limit: 0, Current Usage: 0, Additional Required: 2, (Minimum) New Limit Required: 2. Setup Alerts when Quota reaches threshold. Learn more at https://aka.ms/quotamonitoringalerting . Submit a request for Quota increase at [[https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/{"subscriptionId":"76ba4329-2174-451c-8319-9d9eec471a20","command":"openQuotaApprovalBlade","quotas":{"location":"westus2","providerId":"Microsoft.Compute","resourceName":"standardDADSv5Family","quotaRequest":{"properties":{"limit":2,"unit":"Count","name":{"value":"standardDADSv5Family"}}}}]}](https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%2276ba4329-2174-451c-8319-9d9eec471a20%22,%22command%22:%22openQuotaApprovalBlade%22,%22quotas%22:%5B%7B%22location%22:%22westus2%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDADSv5Family%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:2,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDADSv5Family%22%7D%7D%7D%7D%5D%7D) by specifying parameters listed in the ‘Details’ section for deployment to succeed. Please read more about quota limits at [https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests"}],"message":"The](https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests%22%7D%5D,%22message%22:%22The) template deployment 'Microsoft.Template-20240507202059' is not valid according to the validation procedure. The tracking id is 'ddcae37e-7352-4e2a-bcd3-074e5783b003'. See inner errors for details."}

Make it clear that resource names mentioned in the screenshots may not match their own experience.

Mirroring the same functionality as Synapse analytics integration.

• Update content within module (including screenshots).

• Walk through the set up of private endpoints.

Module 8 - connecting to storage account for metrics. Only shows the storage accounts in the same location as the Purview account - we need to be clear about this in the lab

Split Module 9 into 9A / 9B – Azure Data Factory / Azure Synapse Analytics.

• Update content within module (including screenshots).

• Update content within module (including screenshots).

Module 5 - end of step 3 - section 4 - additional screen missing (ignore screen below)

Update the README with indicative cost of running the lab.

Did you know to cover C0/C1/D0 snippet (currently missing).

Pls replace the region in the template with another region in the One-Click template that doesn't have the restriction to smoothen the deployment.

Issue Description

The parameter randomString depends on the first 6 digits of the resource group ID. Also, adminPassword of SQL VM depends on the parameter randomString.

The first 6 digits of the resource group ID is sometimes composed only of numbers. In this case, the requirement of adminPassword of SQL VM cannot be satisfied and deployment of SQL VM fails.

Workaround Idea

To meet the requirement, the adminPassword of the SQL VM already contains an exclamation as a special character.
Similarly, the above issue can be avoided by putting one or more fixed lower and upper case alphabetical characters into the adminPassword.

Module 5 step 3 also has another step

Module 13 Task 2 step 3 we are getting a different output than expected. But we proceeded with the next step and got the expected results as shown in the screenshot.

Please let us know if we are missing something.

Attaching the screenshot of the issue which we are facing below:

Not sure if its luck, but I think we should have more unique logic in the name vs just pvlab...

• Create module to walk through the process of setting up, scanning, searching etc. third-party data sources: Oracle, Teradata, AWS S3, etc.

• Update content within module (including screenshots).