[Azure Purview] - add a new Bicep quickstart

mumian · mumian · commit 285bf73d29e6 · 2022-09-12T14:47:08.000-04:00
diff --git a/articles/purview/quickstart-ARM-create-azure-purview.md b/articles/purview/quickstart-ARM-create-azure-purview.md
@@ -11,7 +11,7 @@ ms.custom: mode-arm
 
 # Quickstart: Create a Microsoft Purview (formerly Azure Purview) account using an ARM template
 
-This quickstart describes the steps to deploy a Microsoft Purview (formerly Azure Purview) account using an Azure Resource Manager (ARM) template. 
+This quickstart describes the steps to deploy a Microsoft Purview (formerly Azure Purview) account using an Azure Resource Manager (ARM) template.
 
 After you've created the account, you can begin registering your data sources and using the Microsoft Purview governance portal to understand and govern your data landscape. By connecting to data across your on-premises, multi-cloud, and software-as-a-service (SaaS) sources, the Microsoft Purview Data Map creates an up-to-date map of your information. It identifies and classifies sensitive data, and provides end-to-end data linage. Data consumers are able to discover data across your organization and data administrators are able to audit, secure, and ensure right use of your data.
 
@@ -38,7 +38,7 @@ The template used in this quickstart is from [Azure Quickstart Templates](https:
 
 The following resources are defined in the template:
 
-* Microsoft.Purview/accounts
+* [Microsoft.Purview/accounts](/azure/templates/microsoft.purview/accounts?pivots=deployment-language-arm-template)
 
 The template performs the following tasks:
 
diff --git a/articles/purview/quickstart-bicep-create-azure-purview.md b/articles/purview/quickstart-bicep-create-azure-purview.md
@@ -0,0 +1,115 @@
+---
+title: 'Quickstart: Create a Microsoft Purview (formerly Azure Purview) account using a Bicep file'
+description: This Quickstart describes how to create a Microsoft Purview (formerly Azure Purview) account using a Bicep file.
+author: whhender
+ms.author: whhender
+ms.date: 09/12/2022
+ms.topic: quickstart
+ms.service: purview
+---
+
+# Quickstart: Create a Microsoft Purview (formerly Azure Purview) account using a Bicep file
+
+This quickstart describes the steps to deploy a Microsoft Purview (formerly Azure Purview) account using a Bicep file.
+
+After you've created the account, you can begin registering your data sources and using the Microsoft Purview governance portal to understand and govern your data landscape. By connecting to data across your on-premises, multi-cloud, and software-as-a-service (SaaS) sources, the Microsoft Purview Data Map creates an up-to-date map of your information. It identifies and classifies sensitive data, and provides end-to-end data linage. Data consumers are able to discover data across your organization and data administrators are able to audit, secure, and ensure right use of your data.
+
+For more information about the governance capabilities of Microsoft Purview, formerly Azure Purview, [see our overview page](overview.md). For more information about deploying Microsoft Purview across your organization, [see our deployment best practices](deployment-best-practices.md)
+
+To deploy a Microsoft Purview account to your subscription using a Bicep file, follow the guide below.
+
+[!INCLUDE [purview-quickstart-prerequisites](includes/purview-quickstart-prerequisites.md)]
+
+## Review the Bicep file
+
+The Bicep file used in this quickstart is from [Azure Quickstart Templates](https://azure.microsoft.com/resources/templates/data-share-share-storage-account/).
+
+<!--- Below link needs to be updated to Purview quickstart, which I'm currently working on. --->
+:::code language="bicep" source="~/quickstart-templates/quickstarts/microsoft.azurepurview/azure-purview-deployment/main.bicep":::
+
+The following resources are defined in the Bicep file:
+
+* [Microsoft.Purview/accounts](/azure/templates/microsoft.purview/accounts?pivots=deployment-language-bicep)
+
+The Bicep file performs the following tasks:
+
+* Creates a Microsoft Purview account in the specified resource group.
+
+## Deploy the Bicep file
+
+1. Save the Bicep file as **main.bicep** to your local computer.
+1. Deploy the Bicep file using either Azure CLI or Azure PowerShell.
+
+    # [CLI](#tab/CLI)
+
+    ```azurecli
+    az group create --name exampleRG --location eastus
+    az deployment group create --resource-group exampleRG --template-file main.bicep
+    ```
+
+    # [PowerShell](#tab/PowerShell)
+
+    ```azurepowershell
+    New-AzResourceGroup -Name exampleRG -Location eastus
+    New-AzResourceGroupDeployment -ResourceGroupName exampleRG -TemplateFile ./main.bicep
+    ```
+
+    ---
+
+You will be prompted to enter the following values:
+
+* Purview name: enter a name for the Azure Purview account.
+
+When the deployment finishes, you should see a message indicating the deployment succeeded.
+
+## Open Microsoft Purview governance portal
+
+After your Microsoft Purview account is created, you'll use the Microsoft Purview governance portal to access and manage it. There are two ways to open Microsoft Purview governance portal:
+
+* Open your Microsoft Purview account in the [Azure portal](https://portal.azure.com). Select the "Open Microsoft Purview governance portal" tile on the overview page.
+    :::image type="content" source="media/create-catalog-portal/open-purview-studio.png" alt-text="Screenshot showing the Microsoft Purview account overview page, with the Microsoft Purview governance portal tile highlighted.":::
+
+* Alternatively, you can browse to [https://web.purview.azure.com](https://web.purview.azure.com), select your Microsoft Purview account, and sign in to your workspace.
+
+## Get started with your Purview resource
+
+After deployment, the first activities are usually:
+
+* [Create a collection](quickstart-create-collection.md)
+* [Register a resource](azure-purview-connector-overview.md)
+* [Scan the resource](concept-scans-and-ingestion.md)
+
+At this time, these actions aren't able to be taken through an Azure Resource Manager template. Follow the guides above to get started!
+
+## Clean up resources
+
+When you no longer need them, use the Azure portal, Azure CLI, or Azure PowerShell to remove the resource group, firewall, and all related resources.
+
+# [CLI](#tab/CLI)
+
+```azurecli-interactive
+az group delete --name exampleRG
+```
+
+# [PowerShell](#tab/PowerShell)
+
+```azurepowershell-interactive
+Remove-AzResourceGroup -Name exampleRG
+```
+
+---
+
+## Next steps
+
+In this quickstart, you learned how to create a Microsoft Purview (formerly Azure Purview) account and how to access the Microsoft Purview governance portal.
+
+Next, you can create a user-assigned managed identity (UAMI) that will enable your new Microsoft Purview account to authenticate directly with resources using Azure Active Directory (Azure AD) authentication.
+
+To create a UAMI, follow our [guide to create a user-assigned managed identity](manage-credentials.md#create-a-user-assigned-managed-identity).
+
+Follow these next articles to learn how to navigate the Microsoft Purview governance portal, create a collection, and grant access to Microsoft Purview:
+
+> [!div class="nextstepaction"]
+> [Using the Microsoft Purview governance portal](use-azure-purview-studio.md)
+> [Create a collection](quickstart-create-collection.md)
+> [Add users to your Microsoft Purview account](catalog-permissions.md)
diff --git a/articles/purview/toc.yml b/articles/purview/toc.yml
@@ -18,6 +18,8 @@ items:
       href: create-azure-purview-dotnet.md
     - name: Create an account - Python
       href: create-azure-purview-python.md
+    - name: Create an account - Bicep
+      href: quickstart-bicep-create-azure-purview.md
     - name: Create an account - ARM
       href: quickstart-ARM-create-azure-purview.md
   - name: Create a collection - Azure portal
@@ -60,22 +62,22 @@ items:
     items:
       - name: Accounts architecture best practices
         href: concept-best-practices-accounts.md
-      - name: Accounts - Default account 
+      - name: Accounts - Default account
         href: concept-default-purview-account.md
       - name: Asset lifecycle best practices
         href: concept-best-practices-asset-lifecycle.md
-      - name: Automation best practices 
+      - name: Automation best practices
         href: concept-best-practices-automation.md
       - name: Backup, recovery and migration best practices
         href: concept-best-practices-migration.md
-      - name: Classification best practices 
-        href: concept-best-practices-classification.md 
+      - name: Classification best practices
+        href: concept-best-practices-classification.md
       - name: Collections architecture best practices
         href: concept-best-practices-collections.md
       - name: Deployment best practices
         href: deployment-best-practices.md
       - name: Glossary best practices
-        href: concept-best-practices-glossary.md        
+        href: concept-best-practices-glossary.md
       - name: Labeling best practices
         href: concept-best-practices-sensitivity-labels.md
       - name: Lineage best practices
@@ -84,16 +86,16 @@ items:
         href: concept-best-practices-network.md
       - name: Pricing guidelines
         items:
-        - name: Pricing guidelines overview 
+        - name: Pricing guidelines overview
           href: concept-guidelines-pricing.md
         - name: Data map pricing
           href: concept-guidelines-pricing-data-map.md
         - name: Data Estate Insights pricing
           href: concept-guidelines-pricing-data-estate-insights.md
-      - name: Scanning best practices 
+      - name: Scanning best practices
         href: concept-best-practices-scanning.md
       - name: Security best practices
-        href: concept-best-practices-security.md  
+        href: concept-best-practices-security.md
   - name: Permissions and access
     href: catalog-permissions.md
   - name: Data map
@@ -111,7 +113,7 @@ items:
   - name: Data catalog
     items:
     - name: Business glossary
-      href: concept-business-glossary.md 
+      href: concept-business-glossary.md
     - name: Asset normalization
       href: concept-asset-normalization.md
     - name: Workflows
@@ -139,7 +141,7 @@ items:
   - name: Manage collections
     href: how-to-create-and-manage-collections.md
   - name: Manage sources
-    items: 
+    items:
     - name: Supported sources
       href: microsoft-purview-connector-overview.md
     - name: Manage data sources
@@ -154,7 +156,7 @@ items:
     - name: Request access to data asset
       href: how-to-request-access.md
   - name: Sources
-    items: 
+    items:
     - name: Azure Multiple Source
       href: register-scan-azure-multiple-sources.md
     - name: Azure Synapse Analytics workspaces
@@ -173,7 +175,7 @@ items:
       displayName: Register and scan an Azure database for MySQL
     - name: Azure Database for PostgreSQL
       href: register-scan-azure-postgresql.md
-      displayName: Register and scan an Azure database for PostgreSQL        
+      displayName: Register and scan an Azure database for PostgreSQL
     - name: Azure Data Explorer
       href: register-scan-azure-data-explorer.md
       displayName: Register and scan Azure Data Explorer Kusto
@@ -182,7 +184,7 @@ items:
       displayName: Register and scan Azure Data Lake Storage Gen 1 ADLS
     - name: Azure Data Lake Storage Gen 2
       href: register-scan-adls-gen2.md
-      displayName: Register and scan Azure Data Lake Storage Gen 2 ADLS 
+      displayName: Register and scan Azure Data Lake Storage Gen 2 ADLS
     - name: Azure SQL Database
       href: register-scan-azure-sql-database.md
       displayName: Register and scan Azure SQL DB
@@ -229,13 +231,13 @@ items:
       href: register-scan-sap-bw.md
     - name: SAP ECC
       href: register-scan-sapecc-source.md
-    - name: SAP HANA 
+    - name: SAP HANA
       href: register-scan-sap-hana.md
-    - name: SAP S/4HANA 
+    - name: SAP S/4HANA
       href: register-scan-saps4hana-source.md
     - name: Snowflake
       href: register-scan-snowflake.md
-    - name: Teradata 
+    - name: Teradata
       href: register-scan-teradata-source.md
     - name: Amazon RDS
       href: register-scan-amazon-rds.md
@@ -265,7 +267,7 @@ items:
       href: how-to-certify-assets.md
     - name: Managed attributes
       href: how-to-managed-attributes.md
-  - name: Lineage 
+  - name: Lineage
     items:
     - name: Lineage user guide
       href: catalog-lineage-user-guide.md
@@ -286,9 +288,9 @@ items:
     - name: Create & manage terms
       href: how-to-create-import-export-glossary.md
     - name: Manage term templates
-      href: how-to-manage-term-templates.md   
+      href: how-to-manage-term-templates.md
   - name: Classify
-    items: 
+    items:
     - name: Create custom classifications
       href: create-a-custom-classification-and-classification-rule.md
     - name: Apply classifications
@@ -334,11 +336,11 @@ items:
       - name: Isolate network for account and portal
         href: catalog-private-link-account-portal.md
       - name: Managed virtual network
-        href: catalog-managed-vnet.md        
+        href: catalog-managed-vnet.md
       - name: Configure DNS for private endpoint
         href: catalog-private-link-name-resolution.md
       - name: Troubleshoot private endpoints
-        href: catalog-private-link-troubleshoot.md                     
+        href: catalog-private-link-troubleshoot.md
       - name: Private endpoint and Managed VNets FAQ
         href: catalog-private-link-faqs.md
     - name: Deployment exceptions
