Merge pull request #249009 from MicrosoftDocs/main

8/22/2023 AM Publish

Author: Taojunshen

articles/active-directory/devices/howto-vm-sign-in-azure-ad-windows.md

@@ -94,7 +94,7 @@ There are two ways to enable Azure AD login for your Windows VM:
 - Azure Cloud Shell, when you're creating a Windows VM or using an existing Windows VM.
 
 > [!NOTE]
-> If a device object with the same displayMame as the hostname of a VM where an extension is installed exists, the VM fails to join Azure AD with a hostname duplication error. Avoid duplication by [modifying the hostname](../../virtual-network/virtual-networks-viewing-and-modifying-hostnames.md#modify-a-hostname).
+> If a device object with the same displayName as the hostname of a VM where an extension is installed exists, the VM fails to join Azure AD with a hostname duplication error. Avoid duplication by [modifying the hostname](../../virtual-network/virtual-networks-viewing-and-modifying-hostnames.md#modify-a-hostname).
 
 ### Azure portal
 

articles/active-directory/verifiable-credentials/using-wallet-library.md

@@ -115,14 +115,14 @@ Then, you have to handle the following major tasks in your app.
 - User Interface. Any visual representation of stored credentials and the UI for driving the issuance and presentation process must be implemented by you. 
 
 ## Wallet Library Demo app
-The Wallet Library comes with a demo app in the github repo that is ready to use without any modifications. You just have to build and deploy it. The demo app is a lightweight and simple implementation that illustrates issuance and presentation at its minimum. To quickly get going, you can use the QR Code Reader app to scan the QR code, and then copy and paste it into the demo app.
+The Wallet Library comes with a demo app in the GitHub repo that is ready to use without any modifications. You just have to build and deploy it. The demo app is a lightweight and simple implementation that illustrates issuance and presentation at its minimum. To quickly get going, you can use the QR Code Reader app to scan the QR code, and then copy and paste it into the demo app.
 
 In order to test the demo app, you need a webapp that issues credentials and makes presentation requests for credentials. The [Woodgrove public demo webapp](https://aka.ms/vcdemo) is used for this purpose in this tutorial.
 
 ## Building the Android sample
 On your developer machine with Android Studio, do the following:
 
-1. Download or clone the Android Wallet Library [github repo](https://github.com/microsoft/entra-verifiedid-wallet-library-android/archive/refs/heads/dev.zip). 
+1. Download or clone the Android Wallet Library [GitHub repo](https://github.com/microsoft/entra-verifiedid-wallet-library-android/archive/refs/heads/dev.zip). 
 You don’t need the walletlibrary folder and you can delete it if you like.
 1. Start Android Studio and open the parent folder of walletlibrarydemo
 
@@ -169,7 +169,7 @@ The sample app holds the issued credential in memory, so after issuance, you can
 
 ## Building the iOS sample
 On your Mac developer machine with Xcode, do the following:
-1. Download or clone the iOS Wallet Library [github repo](https://github.com/microsoft/entra-verifiedid-wallet-library-ios/archive/refs/heads/dev.zip). 
+1. Download or clone the iOS Wallet Library [GitHub repo](https://github.com/microsoft/entra-verifiedid-wallet-library-ios/archive/refs/heads/dev.zip). 
 1. Start Xcode and open the top level folder for the WalletLibrary
 1. Set focus on WalletLibraryDemo project
 

articles/azure-arc/kubernetes/workload-management.md

@@ -34,7 +34,7 @@ To deploy the sample, run the following script:
 mkdir kalypso && cd kalypso
 curl -fsSL -o deploy.sh https://raw.githubusercontent.com/microsoft/kalypso/main/deploy/deploy.sh
 chmod 700 deploy.sh
-./deploy.sh -c -p <prefix. e.g. kalypso> -o <github org. e.g. eedorenko> -t <github token> -l <azure-location. e.g. westus2> 
+./deploy.sh -c -p <prefix. e.g. kalypso> -o <GitHub org. e.g. eedorenko> -t <GitHub token> -l <azure-location. e.g. westus2> 
 ```
 
 This script may take 10-15 minutes to complete. After it's done, it reports the execution result in the output like this:
@@ -59,7 +59,7 @@ Created AKS clusters in kalypso-rg resource group:
 > If something goes wrong with the deployment, you can delete the created resources with the following command:
 > 
 > ```bash
-> ./deploy.sh -d -p <preix. e.g. kalypso> -o <github org. e.g. eedorenko> -t <github token> -l <azure-location. e.g. westus2> 
+> ./deploy.sh -d -p <preix. e.g. kalypso> -o <GitHub org. e.g. eedorenko> -t <GitHub token> -l <azure-location. e.g. westus2> 
 > ```
 
 ### Sample overview
@@ -163,7 +163,7 @@ With this file, Application Team requests Kubernetes compute resources from the
 To register the application, open a terminal and use the following script: 
 
 ```bash
-export org=<github org>
+export org=<GitHub org>
 export prefix=<prefix>
 
 # clone the control-plane repo
@@ -317,7 +317,7 @@ spec:
     branch: dev
   secretRef:
     name: repo-secret
-  url: https://github.com/<github org>/<prefix>-app-gitops
+  url: https://github.com/<GitHub org>/<prefix>-app-gitops
 ---
 apiVersion: kustomize.toolkit.fluxcd.io/v1beta2
 kind: Kustomization
@@ -550,7 +550,7 @@ When no longer needed, delete the resources that you created. To do so, run the
 
 ```bash
 # In kalypso folder
-./deploy.sh -d -p <preix. e.g. kalypso> -o <github org. e.g. eedorenko> -t <github token> -l <azure-location. e.g. westus2> 
+./deploy.sh -d -p <preix. e.g. kalypso> -o <GitHub org. e.g. eedorenko> -t <GitHub token> -l <azure-location. e.g. westus2> 
 ```
 
 ## Next steps

articles/azure-monitor/containers/monitor-kubernetes.md

@@ -280,7 +280,7 @@ In addition to developing the application, the *developer* maintains the applica
 
 ### Azure services for developer
 
-The following table lists the services that are commonly used by the network engineer to monitor the health and performance of the Kubernetes cluster and its components.  
+The following table lists the services that are commonly used by the developer to monitor the health and performance of the Kubernetes cluster and its components.  
 
 
 | Service | Description |

articles/azure-monitor/essentials/diagnostic-settings.md

@@ -136,6 +136,13 @@ The following table provides unique requirements for each destination including
 | Event Hubs | The shared access policy for the namespace defines the permissions that the streaming mechanism has. Streaming to Event Hubs requires Manage, Send, and Listen permissions. To update the diagnostic setting to include streaming, you must have the ListKey permission on that Event Hubs authorization rule.<br><br>The event hub namespace needs to be in the same region as the resource being monitored if the resource is regional. <br><br> Diagnostic settings can't access Event Hubs resources when virtual networks are enabled. You must enable **Allow trusted Microsoft services** to bypass this firewall setting in Event Hubs so that the Azure Monitor diagnostic settings service is granted access to your Event Hubs resources.|
 | Partner integrations | The solutions vary by partner. Check the [Azure Monitor partner integrations documentation](../../partner-solutions/overview.md) for details.
 
+> [!CAUTION]
+> If you want to store diagnostic logs in a Log Analytics workspace, there are two points to consider to avoid seeing duplicate data in Application Insights:
+> * The destination can't be the same Log Analytics workspace that your Application Insights resource is based on.
+> * The Application Insights user can't have access to both workspaces. Set the Log Analytics access control mode to Requires workspace permissions. Through Azure role-based access control, ensure the user only has access to the Log Analytics workspace the Application Insights resource is based on.
+>
+> These steps are necessary because Application Insights accesses telemetry across Application Insight resources, including Log Analytics workspaces, to provide complete end-to-end transaction operations and accurate application maps. Because diagnostic logs use the same table names, duplicate telemetry can be displayed if the user has access to multiple resources that contain the same data.
+
 ## Controlling costs
 
 There is a cost for collecting data in a Log Analytics workspace, so you should only collect the categories you require for each service. The data volume for resource logs varies significantly between services, 

articles/confidential-computing/TOC.yml

@@ -136,7 +136,7 @@
       href: key-rotation-offline.md
     - name: Use sample app with guest attestation
       href: guest-attestation-example.md
-    - name: How to leverage virtual TPMs in Azure confidential VMs
+    - name: Leverage virtual TPMs in Azure confidential VMs
       href: how-to-leverage-virtual-tpms-in-azure-confidential-vms.md
     - name: Create a custom image for a confidential VM
       href: how-to-create-custom-image-confidential-vm.md

articles/confidential-computing/how-to-leverage-virtual-tpms-in-azure-confidential-vms.md

@@ -1,5 +1,5 @@
 ---
-title: How to leverage virtual TPMs in Azure confidential VMs
+title: Leverage virtual TPMs in Azure confidential VMs
 description: Learn how to use the vTPM benefits after building trust in a confidential VM.
 author: simranparkhe
 ms.service: virtual-machines
@@ -11,7 +11,7 @@ ms.author: simranparkhe
 ms.custom: devx-track-azurecli
 ---
 
-# How to leverage virtual TPMs in Azure confidential VMs
+# Leverage virtual TPMs in Azure confidential VMs
 
 **Applies to:** :heavy_check_mark: Linux VMs
 

articles/container-apps/blue-green-deployment.md

@@ -40,7 +40,7 @@ After you test and verify the new revision, you can then point production traffi
 This article shows you how to implement blue-green deployment in a container app. To run the following examples, you need a container app environment where you can create a new app.
 
 > [!NOTE]
-> Refer to [containerapps-blue-green repository](https://github.com/Azure-Samples/containerapps-blue-green) for a complete example of a github workflow that implements blue-green deployment for Container Apps.
+> Refer to [containerapps-blue-green repository](https://github.com/Azure-Samples/containerapps-blue-green) for a complete example of a GitHub workflow that implements blue-green deployment for Container Apps.
 
 ## Create a container app with multiple active revisions enabled
 

articles/container-instances/container-instances-resource-and-quota-limits.md

@@ -50,15 +50,14 @@ The following limits are default limits that can’t be increased through a quot
 | Resource | Actual Limit | 
 | --- | :--- | 
 | Standard sku container groups per region per subscription | 100 | 
-| Standard sku cores (CPUs) per region per subscription | 100 | 
-| Standard sku cores (CPUs) for K80 GPU per region per subscription | 0 | 
+| Standard sku cores (CPUs) per region per subscription | 100 |  
 | Standard sku cores (CPUs) for V100 GPU per region per subscription | 0 | 
 | Container group creates per hour |300<sup>1</sup> | 
 | Container group creates per 5 minutes | 100<sup>1</sup> | 
 | Container group deletes per hour | 300<sup>1</sup> | 
 | Container group deletes per 5 minutes | 100<sup>1</sup> | 
 
-## Standard Core Resources 
+## Standard Container Resources 
 
 ### Linux Container Groups 
 
@@ -91,7 +90,29 @@ The following resources are available in all Azure Regions supported by Azure Co
 | :----: | :-----: | :-------: | 
 | 4 | 16 | 20 | Y | 
 
-## GPU Resources (Preview) 
+## Spot Container Resources (Preview)
+
+The following maximum resources are available to a container group deployed using [Spot Containers](container-instances-spot-containers-overview.md) (preview). 
+
+> [!NOTE]
+> Spot Containers are only available in the following regions at this time: East US 2, West Europe, and West US.
+
+| Max CPU | Max Memory (GB) | VNET Max CPU | VNET Max Memory (GB) | Storage (GB) | 
+| :---: | :---: | :----: | :-----: | :-------: |
+| 4 | 16 | N/A | N/A | 50 | 
+
+## Confidential Container Resources (Preview)
+
+The following maximum resources are available to a container group deployed using [Confidential Containers](container-instances-confidential-overview.md) (preview).
+
+> [!NOTE]
+> Confidential Containers are only available in the following regions at this time: East US, North Europe, West Europe, and West US.
+
+| Max CPU | Max Memory (GB) | VNET Max CPU | VNET Max Memory (GB) | Storage (GB) | 
+| :---: | :---: | :----: | :-----: | :-------: |
+| 4 | 16 | 4 | 16 | 50 | 
+
+## GPU Container Resources (Preview) 
 > [!IMPORTANT]
 > K80 and P100 GPU SKUs are retiring by August 31st, 2023. This is due to the retirement of the underlying VMs used: [NC Series](../virtual-machines/nc-series-retirement.md) and [NCv2 Series](../virtual-machines/ncv2-series-retirement.md) Although V100 SKUs will be available, it is receommended to use Azure Kubernetes Service instead. GPU resources are not fully supported and should not be used for production workloads. Use the following resources to migrate to AKS today: [How to Migrate to AKS](../aks/aks-migration.md).
 

articles/internet-analyzer/index.yml

@@ -9,7 +9,7 @@ metadata:
   services: internet-analyzer
   ms.service: internet-analyzer
   ms.topic: landing-page
-  author: megan-beatty #github alias
+  author: megan-beatty #GitHub alias
   ms.author: mebeatty
   ms.date: 10/16/2019