Skip to content

Commit

Permalink
Update Purview Known Error (#170)
Browse files Browse the repository at this point in the history
* Purview misspelt as Pruview

Purview misspelt as Pruview.

* Added more details to known error

Co-authored-by: Marvin Buss <34542414+marvinbuss@users.noreply.github.com>
  • Loading branch information
amanjeetsingh and marvinbuss authored Sep 14, 2021
1 parent 9b64793 commit 57104d2
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/EnterpriseScaleAnalytics-KnownIssues.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ This error message appears, if the Purview soft-limit has been reached inside yo
**Solution:**
This error message appears, when deploying Purview and the `Microsoft.EventHub`, `Microsoft.Storage` and `Microsoft.Pruview` Resource Provider has not been registered on the subscription. We have released a fix to our Deploy To Azure Buttons to overcome this issue until it gets fixed on the Purview side. If you still run into this problem, please open an Issue in this repo and start registering the three Resource Providers manually through the `Azure Portal`, `Azure Powershell` or `Azure CLI` as mentioned [here](https://docs.microsoft.com/azure/azure-resource-manager/management/resource-providers-and-types). Once that is done, use the "Redeploy" button on the failed deployment to restart the deployment and successfuly deploy the components.
This error message appears, when deploying Purview and the `Microsoft.EventHub`, `Microsoft.Storage` and/or `Microsoft.Purview` Resource Provider has not been registered on the subscription or has been registered during an early Preview phase. We have released a fix to our Deploy To Azure Buttons to overcome this issue until it gets fixed on the Purview side. If you still run into this problem, please open an Issue in this repo and start (re-)registering the three Resource Providers manually through the `Azure Portal`, `Azure Powershell` or `Azure CLI` as mentioned [here](https://docs.microsoft.com/azure/azure-resource-manager/management/resource-providers-and-types). Once that is done, use the "Redeploy" button on the failed deployment to restart the deployment and successfuly deploy the components.
>[Previous (Option (a) GitHub Actions)](/docs/EnterpriseScaleAnalytics-GitHubActionsDeployment.md)
>[Previous (Option (b) Azure DevOps)](/docs/EnterpriseScaleAnalytics-AzureDevOpsDeployment.md)

0 comments on commit 57104d2

Please sign in to comment.