Merge pull request #194559 from MicrosoftDocs/main

4/08 AM Publish

Author: huypub

.openpublishing.redirection.azure-monitor.json

@@ -42,12 +42,17 @@
         },
         {
             "source_path_from_root": "/articles/azure-monitor/app/pricing.md",
-            "redirect_url": "/azure/azure-monitor/logs/cost-logs.md",
+            "redirect_url": "/azure/azure-monitor/logs/cost-logs",
             "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/azure-monitor/logs/manage-cost-storage.md",
-            "redirect_url": "/azure/azure-monitor/logs/cost-logs.md",
+            "redirect_url": "/azure/azure-monitor/logs/cost-logs",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/logs/data-ingestion-from-file.md",
+            "redirect_url": "/azure/azure-monitor/agents/data-sources-custom-logs",
             "redirect_document_id": false
         }
     ]

articles/active-directory/verifiable-credentials/whats-new.md

@@ -20,14 +20,15 @@ This article lists the latest features, improvements, and changes in the Azure A
 
 ## March 2022
 - Azure AD Verifiable Credentials customers can now change the [domain linked](how-to-dnsbind.md) to their DID easily from the Azure Portal.
+- We made updates to Microsoft Authenticator that change the interaction between the Issuer of a verifiable credential and the user presenting the verifiable credential. This update forces all Verifiable Credentials to be reissued in Microsoft Authenticator for iOS. [More information](whats-new.md?#microsoft-authenticator-did-generation-update)
 
 ## February 2022
 
 We are rolling out some breaking changes to our service. These updates require Azure AD Verifiable Credentials service reconfiguration. End-users need to have their verifiable credentials reissued.
 
 - The Azure AD Verifiable Credentials service can now store and handle data processing in the Azure European region. [More information](whats-new.md?#azure-ad-verifiable-credentials-available-in-europe)
 - Azure AD Verifiable Credentials customers can take advantage of enhancements to credential revocation. These changes add a higher degree of privacy through the implementation of the [W3C Status List 2021](https://w3c-ccg.github.io/vc-status-list-2021/) standard. [More information](whats-new.md?#credential-revocation-with-enhanced-privacy)
-- We made updates to Microsoft Authenticator that change the interaction between the Issuer of a verifiable credential and the user presenting the verifiable credential. This update forces all Verifiable Credentials to be reissued in Microsoft Authenticator for Android. [More information](whats-new.md?#microsoft-authenticator-android-did-generation-update)
+- We made updates to Microsoft Authenticator that change the interaction between the Issuer of a verifiable credential and the user presenting the verifiable credential. This update forces all Verifiable Credentials to be reissued in Microsoft Authenticator for Android. [More information](whats-new.md?#microsoft-authenticator-did-generation-update)
 
 >[!IMPORTANT]
 > All Azure AD Verifiable Credential customers receiving a banner notice in the Azure portal need to go through a service reconfiguration before March 31st 2022. On March 31st 2022 tenants that have not been reconfigured will lose access to any previous configuration. Administrators will have to set up a new instance of the Azure AD Verifiable Credential service. Learn more about how to [reconfigure your tenant](verifiable-credentials-faq.md?#how-do-i-reconfigure-the-azure-ad-verifiable-credentials-service).
@@ -100,9 +101,9 @@ Sample contract file:
 >[!IMPORTANT]
 > You have to reconfigure your Azure AD Verifiable Credential service instance to create your new Identity hub endpoint. You have until March 31st 2022, to schedule and manage the reconfiguration of your deployment. On March 31st, 2022 deployments that have not been reconfigured will lose access to any previous Azure AD Verifiable Credentials service configuration. Administrators will need to set up a new service instance.
 
-### Microsoft Authenticator Android DID Generation Update
+### Microsoft Authenticator DID Generation Update
 
-We are making protocol updates in Microsoft Authenticator to support Single Long Form DID, thus deprecating the use of pairwise. With this update, your DID in Microsoft Authenticator will be used of every issuer and relaying party exchange. Holders of verifiable credentials using Microsoft Authenticator for Android must get their verifiable credentials reissued as any previous credentials aren't going to continue working.
+We are making protocol updates in Microsoft Authenticator to support Single Long Form DID, thus deprecating the use of pairwise. With this update, your DID in Microsoft Authenticator will be used of every issuer and relaying party exchange. Holders of verifiable credentials using Microsoft Authenticator must get their verifiable credentials reissued as any previous credentials aren't going to continue working.
 
 ## December 2021
 

articles/attestation/quickstart-Bicep.md

@@ -0,0 +1,98 @@
+---
+title: Create an Azure Attestation certificate by using Bicep
+description: Learn how to create an Azure Attestation certificate by using Bicep.
+services: azure-resource-manager
+author: mumian
+ms.service: attestation
+ms.topic: quickstart
+ms.custom: subject-armqs, devx-track-azurepowershell, mode-arm
+ms.author: jgao
+ms.date: 03/08/2022
+---
+
+# Quickstart: Create an Azure Attestation provider with a Bicep file
+
+[Microsoft Azure Attestation](overview.md) is a solution for attesting Trusted Execution Environments (TEEs). This quickstart focuses on the process of deploying a Bicep file to create a Microsoft Azure Attestation policy.
+
+[!INCLUDE [About Bicep](../../includes/resource-manager-quickstart-bicep-introduction.md)]
+
+## Prerequisites
+
+If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
+
+## Review the Bicep file
+
+The Bicep file used in this quickstart is from [Azure Quickstart Templates](https://azure.microsoft.com/resources/templates/attestation-provider-create/).
+
+:::code language="bicep" source="~/quickstart-templates/quickstarts/microsoft.attestation/attestation-provider-create/main.bicep":::
+
+Azure resources defined in the Bicep file:
+
+- [Microsoft.Attestation/attestationProviders](/azure/templates/microsoft.attestation/attestationproviders?tabs=bicep)
+
+## 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
+    ```
+
+    ---
+
+    When the deployment finishes, you should see a message indicating the deployment succeeded.
+
+## Validate the deployment
+
+Use the Azure portal, Azure CLI, or Azure PowerShell to verify the resource group and server resource were created.
+
+# [CLI](#tab/CLI)
+
+```azurecli-interactive
+az resource list --resource-group exampleRG
+```
+
+# [PowerShell](#tab/PowerShell)
+
+```azurepowershell-interactive
+Get-AzResource -ResourceGroupName exampleRG
+```
+
+---
+
+## Clean up resources
+
+Other Azure Attestation build upon this quickstart. If you plan to continue on to work with subsequent quickstarts and tutorials, you may wish to leave these resources in place.
+
+When no longer needed, delete the resource group, which deletes the Attestation resource. To delete the resource group by using Azure CLI or Azure PowerShell:
+
+# [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 created an attestation resource using a Bicep file, and validated the deployment. To learn more about Azure Attestation, see [Overview of Azure Attestation](overview.md).

articles/attestation/toc.yml

@@ -1,4 +1,4 @@
-- name: Microsoft Azure Attestation 
+- name: Microsoft Azure Attestation
   href: index.yml
 - name: Overview
   items:
@@ -7,6 +7,9 @@
 - name: Quickstarts
   expanded: true
   items:
+  - name: Bicep
+    displayName: Resource Manager, ARM
+    href: quickstart-bicep.md
   - name: ARM template
     displayName: Resource Manager
     href: quickstart-template.md
@@ -21,7 +24,7 @@
   - name: Authoring an attestation policy
     href: author-sign-policy.md
   - name: Create a Private Endpoint - PowerShell
-    href: private-endpoint-powershell.md 
+    href: private-endpoint-powershell.md
   - name: Azure Diagnostic Monitoring
     href: azure-diagnostic-monitoring.md
   - name: SGX attestation code samples

articles/azure-arc/data/version-log.md

@@ -24,8 +24,8 @@ This article identifies the component versions with each release of Azure Arc-en
 |CRD names and versions	|`datacontrollers.arcdata.microsoft.com`: v1beta1, v1, v2, v3, v4</br>`exporttasks.tasks.arcdata.microsoft.com`: v1beta1, v1, v2</br>`kafkas.arcdata.microsoft.com`: v1beta1</br>`monitors.arcdata.microsoft.com`: v1beta1, v1, v2</br>`sqlmanagedinstances.sql.arcdata.microsoft.com`: v1beta1, v1, v2, v3, v4</br>`postgresqls.arcdata.microsoft.com`: v1beta1, v1beta2</br>`sqlmanagedinstancerestoretasks.tasks.sql.arcdata.microsoft.com`: v1beta1, v1</br>`failovergroups.sql.arcdata.microsoft.com`: v1beta1, v1beta2</br>`activedirectoryconnectors.arcdata.microsoft.com`: v1beta1, v1beta2|
 |ARM API version|2021-11-01|
 |`arcdata` Azure CLI extension version|	1.3.0|
-|Arc enabled Kubernetes helm chart extension version|1.1.19091004|
-|Arc Data extension for Azure Data Studio|1.0|
+|Arc enabled Kubernetes helm chart extension version|1.1.19211001|
+|Arc Data extension for Azure Data Studio|1.1.0|
 
 ## March 08, 2022
 

articles/azure-monitor/containers/container-insights-enable-existing-clusters.md

@@ -91,7 +91,7 @@ If you would rather integrate with an existing workspace, perform the following
 
 ## Enable using Terraform
 
-1. Add the **oms_agent** add-on profile to the existing [azurerm_kubernetes_cluster resource](https://www.terraform.io/docs/providers/azurerm/d/kubernetes_cluster.html#addon_profile)
+1. Add the **oms_agent** add-on profile to the existing [azurerm_kubernetes_cluster resource](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/data-sources/kubernetes_cluster)
 
    ```
    addon_profile {
@@ -102,7 +102,9 @@ If you would rather integrate with an existing workspace, perform the following
    }
    ```
 
-2. Add the [azurerm_log_analytics_solution](https://www.terraform.io/docs/providers/azurerm/r/log_analytics_solution.html) following the steps in the Terraform documentation.
+2. Add the [azurerm_log_analytics_solution](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/log_analytics_solution) following the steps in the Terraform documentation.
+
+3. The metrics are not collected by default through Terraform, so once onboarded, there is an additional step to assign the monitoring metrics publisher role, which is required to [enable the metrics](./container-insights-update-metrics.md#update-one-cluster-by-using-the-azure-cli). 
 
 ## Enable from Azure Monitor in the portal
 

articles/azure-monitor/logs/data-ingestion-from-file.md

@@ -92,11 +92,7 @@ items:
     - name: Container insights
       href: containers/resource-manager-container-insights.md
     - name: Data collection rules
-      items:
-      - name: Data collection rules
-        href: agents/resource-manager-data-collection-rules.md
-      - name: Data puller
-        href: logs/data-ingestion-from-file.md
+      href: agents/resource-manager-data-collection-rules.md
     - name: Diagnostic settings
       href: essentials/resource-manager-diagnostic-settings.md
     - name: Log Analytics workspaces

articles/azure-monitor/toc.yml

@@ -83,6 +83,10 @@
       href: ../../expressroute/quickstart-create-expressroute-vnet-bicep.md?toc=/azure/azure-resource-manager/bicep/toc.json
     - name: Front Door
       href: ../../frontdoor/quickstart-create-front-door-bicep.md?toc=/azure/azure-resource-manager/bicep/toc.json
+  - name: Security
+    items:
+    - name: Attestation
+      href: ../../attestation/quickstart-bicep.md?toc=/azure/azure-resource-manager/bicep/toc.json
   - name: Storage
     items:
     - name: Data Share