Merge pull request #211091 from MicrosoftDocs/repo_sync_working_branch

huypub · web-flow · commit 2d384a8376bd · 2022-09-14T09:45:40.000-07:00
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
diff --git a/articles/azure-arc/data/create-sql-managed-instance.md b/articles/azure-arc/data/create-sql-managed-instance.md
@@ -46,13 +46,13 @@ az sql mi-arc create -n sqldemo --storage-class-backups mybackups --k8s-namespac
 ### [Directly connected mode](#tab/directly)
 
 ```azurecli
-az sql mi-arc create --name <name> --resource-group <group>  --location <Azure location> -–subscription <subscription>  --custom-location <custom-location> --storage-class-backups <RWX capable storageclass>
+az sql mi-arc create --name <name> --resource-group <group> -–subscription <subscription>  --custom-location <custom-location> --storage-class-backups <RWX capable storageclass>
 ```
 
 Example:
 
 ```azurecli
-az sql mi-arc create --name sqldemo --resource-group rg  --location uswest2 -–subscription xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx  --custom-location private-location --storage-class-backups mybackups
+az sql mi-arc create --name sqldemo --resource-group rg -–subscription xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx  --custom-location private-location --storage-class-backups mybackups
 ```
 
 ---
diff --git a/articles/azure-resource-manager/bicep/quickstart-create-bicep-use-visual-studio.md b/articles/azure-resource-manager/bicep/quickstart-create-bicep-use-visual-studio.md
@@ -15,7 +15,7 @@ This quickstart guides you through the steps to create a [Bicep file](overview.m
 
 - Azure Subscription. If you don't have an Azure subscription, [create a free account](https://azure.microsoft.com/free/) before you begin.
 - Visual Studio version 17.3.0 preview 3 or newer.  See [Visual Studio Preview](https://visualstudio.microsoft.com/vs/preview/).
-- Visual Studio Bicep extension.  See [Visual Studio Marketplace](https://marketplace.visualstudio.com/).
+- Visual Studio Bicep extension.  See [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.visualstudiobicep).
 - Bicep file deployment requires either the latest [Azure CLI](/cli/azure/) or the latest [Azure PowerShell module](/powershell/azure/new-azureps-module-az).
 
 ## Add resource snippet
diff --git a/articles/cloud-shell/troubleshooting.md b/articles/cloud-shell/troubleshooting.md
@@ -161,8 +161,8 @@ In order to **export** the user settings Cloud Shell saves for you such as prefe
 Bash:
 
   ```
-  token="Bearer $(curl http://localhost:50342/oauth2/token --data "resource=https://management.azure.com/" -H Metadata:true -s | jq -r ".access_token")"
-  curl https://management.azure.com/providers/Microsoft.Portal/usersettings/cloudconsole?api-version=2017-12-01-preview -H Authorization:"$token" -s | jq
+  token="Bearer $(curl http://localhost:50342/oauth2/token --data "resource=https://management.azure.com/" -H Metadata:true -s | jq -r ".accessToken")"
+  curl https://management.azure.com/providers/Microsoft.Portal/usersettings/cloudconsole?api-version=2017-12-01-preview -H Authorization:"Bearer $token" -s | jq
   ```
 
 PowerShell:
@@ -185,8 +185,8 @@ In order to **delete** your user settings Cloud Shell saves for you such as pref
 Bash:
 
   ```
-  token=(az account get-access-token --resource "https://management.azure.com/" | jq -r ".access_token")
-  curl -X DELETE https://management.azure.com/providers/Microsoft.Portal/usersettings/cloudconsole?api-version=2017-12-01-preview -H Authorization:"$token"
+  token=$(az account get-access-token --resource "https://management.azure.com/" | jq -r ".accessToken")
+  curl -X DELETE https://management.azure.com/providers/Microsoft.Portal/usersettings/cloudconsole?api-version=2017-12-01-preview -H Authorization:"Bearer $token"
   ```
 
 PowerShell:
diff --git a/articles/data-factory/connector-dynamics-crm-office-365.md b/articles/data-factory/connector-dynamics-crm-office-365.md
@@ -58,6 +58,7 @@ For Dynamics 365 specifically, the following application types are supported:
 - Dynamics 365 for Field Service
 - Dynamics 365 for Project Service Automation
 - Dynamics 365 for Marketing
+
 This connector doesn't support other application types like Finance, Operations, and Talent.
 
 >[!TIP]
diff --git a/articles/defender-for-cloud/quickstart-onboard-aws.md b/articles/defender-for-cloud/quickstart-onboard-aws.md
@@ -377,7 +377,7 @@ The following IAM permissions are needed to discover AWS resources:
 | GuardDute | `guardduty:DescribeOrganizationConfiguration` <br> `guardduty:DescribePublishingDestination` <br> `guardduty:List*` |
 | IAM | `iam:Generate*` <br> `iam:Get*` <br> `iam:List*` <br> `iam:Simulate*` |
 | KMS | `kms:Describe*` <br> `kms:List*` |
-| LAMDBA | `lambda:GetPolicy` <br> `lambda:List*` |
+| LAMBDA | `lambda:GetPolicy` <br> `lambda:List*` |
 | Network firewall | `network-firewall:DescribeFirewall` <br> `network-firewall:DescribeFirewallPolicy` <br> `network-firewall:DescribeLoggingConfiguration` <br> `network-firewall:DescribeResourcePolicy` <br> `network-firewall:DescribeRuleGroup` <br> `network-firewall:DescribeRuleGroupMetadata` <br> `network-firewall:ListFirewallPolicies` <br> `network-firewall:ListFirewalls` <br> `network-firewall:ListRuleGroups` <br> `network-firewall:ListTagsForResource` |
 | RDS | `rds:Describe*` <br> `rds:List*` |
 | RedShift | `redshift:Describe*` |
diff --git a/articles/openshift/howto-gpu-workloads.md b/articles/openshift/howto-gpu-workloads.md
@@ -45,7 +45,7 @@ ARO supports the following GPU workers:
 * NC4as T4 v3
 * NC8as T4 v3
 * NC16as T4 v3
-* NC464as T4 v3
+* NC64as T4 v3
 
 > [!NOTE] 
 > When requesting quota, remember that Azure is per core. To request a single NC4as T4 v3 node, you will need to request quota in groups of 4. If you wish to request an NC16as T4 v3, you will need to request quota of 16.
diff --git a/articles/openshift/support-policies-v4.md b/articles/openshift/support-policies-v4.md
@@ -61,10 +61,6 @@ Azure Red Hat OpenShift 4 supports node instances on the following virtual machi
 |G*|Standard_G5|32|448|
 |G|Standard_GS5|32|448|
 |Mms|Standard_M128ms|128|3892|
-|NC4asT4v3|Standard_NC4as_T4_v3|4|28|
-|NC8asT4v3|Standard_NC8as_T4_v3|8|56|
-|NC16asT4v3|Standard_NC16as_T4_v3|16|110|
-|NC64asT4v3|Standard_NC64as_T4_v3|64|440|
 
 \*Does not support Premium_LRS OS Disk, StandardSSD_LRS is used instead
 
@@ -117,7 +113,6 @@ Azure Red Hat OpenShift 4 supports node instances on the following virtual machi
 |Mms|Standard_M128ms|128|3892|
 
 ### Storage optimized
-
 |Series|Size|vCPU|Memory: GiB|
 |-|-|-|-|
 |L4s|Standard_L4s|4|32|
@@ -130,11 +125,19 @@ Azure Red Hat OpenShift 4 supports node instances on the following virtual machi
 |L48s_v2|Standard_L48s_v2|32|384|
 |L64s_v2|Standard_L48s_v2|64|512|
 
+### GPU workload
+|Series|Size|vCPU|Memory: GiB|
+|-|-|-|-|
+|NC4asT4v3|Standard_NC4as_T4_v3|4|28|
+|NC8asT4v3|Standard_NC8as_T4_v3|8|56|
+|NC16asT4v3|Standard_NC16as_T4_v3|16|110|
+|NC64asT4v3|Standard_NC64as_T4_v3|64|440|
+
 ### Memory and storage optimized
 
 |Series|Size|vCPU|Memory: GiB|
 |-|-|-|-|
 |G*|Standard_G5|32|448|
 |G|Standard_GS5|32|448|
 
-\*Does not support Premium_LRS OS Disk, StandardSSD_LRS is used instead
+\*Does not support Premium_LRS OS Disk, StandardSSD_LRS is used instead
diff --git a/articles/sentinel/normalization-develop-parsers.md b/articles/sentinel/normalization-develop-parsers.md
@@ -203,7 +203,7 @@ In many cases, the original value extracted needs to be normalized. For example,
 
 Also, ensuring that parser output fields matches type defined in the schema is critical for parsers to work.  For example, you may need to convert a string representing date and time to a datetime field. Functions such as `todatetime` and `tohex` are helpful in these cases.
 
-For example, the original unique event ID may be sent as an integer, but ASIM requires the value to be a string, to ensure broad compatibility among data sources. Therefore, when assigning the source field use `extned` and `tostring` instead of `project-rename`:
+For example, the original unique event ID may be sent as an integer, but ASIM requires the value to be a string, to ensure broad compatibility among data sources. Therefore, when assigning the source field use `extend` and `tostring` instead of `project-rename`:
 
 ```KQL
   | extend EventOriginalUid = tostring(ReportId),
@@ -500,4 +500,4 @@ Learn more about the ASIM in general:
 - Watch the [Deep Dive Webinar on Microsoft Sentinel Normalizing Parsers and Normalized Content](https://www.youtube.com/watch?v=zaqblyjQW6k) or review the [slides](https://1drv.ms/b/s!AnEPjr8tHcNmjGtoRPQ2XYe3wQDz?e=R3dWeM)
 - [Advanced Security Information Model (ASIM) overview](normalization.md)
 - [Advanced Security Information Model (ASIM) schemas](normalization-about-schemas.md)
-- [Advanced Security Information Model (ASIM) content](normalization-content.md)
+- [Advanced Security Information Model (ASIM) content](normalization-content.md)
diff --git a/articles/storage/blobs/upgrade-to-data-lake-storage-gen2-how-to.md b/articles/storage/blobs/upgrade-to-data-lake-storage-gen2-how-to.md
@@ -1,6 +1,6 @@
 ---
 title: Upgrade Azure Blob Storage with Azure Data Lake Storage Gen2 capabilities  | Microsoft Docs
-description: Shows you how to use Resource Manager templates to upgrade from Azure Blob storage to Data Lake Storage.
+description: Shows you how to use Resource Manager templates to upgrade from Azure Blob Storage to Data Lake Storage.
 author: normesta
 ms.service: storage
 ms.topic: conceptual
diff --git a/articles/virtual-machines/workloads/sap/get-started.md b/articles/virtual-machines/workloads/sap/get-started.md
@@ -66,6 +66,7 @@ In the SAP workload documentation space, you can find the following areas:
 
 ## Change Log
 
+- September 14, 2022 Release of updated SAP on Oracle guide with new and updated content [Azure Virtual Machines Oracle DBMS deployment for SAP workload](./dbms_guide_oracle.md)
 - September 8, 2022: Change in [SAP HANA scale-out HSR with Pacemaker on Azure VMs on SLES](./sap-hana-high-availability-scale-out-hsr-suse.md) to add instructions for deploying /hana/shared (only) on NFS on Azure Files
 - September 6, 2022: Add managed identity for pacemaker fence agent [Set up Pacemaker on SUSE Linux Enterprise Server (SLES) in Azure](high-availability-guide-suse-pacemaker.md) on SLES and [Setting up Pacemaker on RHEL in Azure](high-availability-guide-rhel-pacemaker.md) RHEL
 - August 22, 2022: Release of cost optimization scenario [Deploy PAS and AAS with SAP NetWeaver HA cluster](high-availability-guide-rhel-with-dialog-instance.md) on RHEL
@@ -201,4 +202,4 @@ In the SAP workload documentation space, you can find the following areas:
 - June 23, 2020: Changes to [Azure Virtual Machines planning and implementation for SAP NetWeaver](./planning-guide.md) guide and introduction of [Azure Storage types for SAP workload](./planning-guide-storage.md) guide
 - June 22, 2020: Add installation steps for new VM Extension for SAP to the [Deployment Guide](deployment-guide.md)
 - June 16, 2020: Change in [Public endpoint connectivity for VMs using Azure Standard ILB in SAP HA scenarios](./high-availability-guide-standard-load-balancer-outbound-connections.md) to add a link to SUSE Public Cloud Infrastructure 101 documentation 
-- June 10, 2020: Adding new HLI SKUs into [Available SKUs for HLI](./hana-available-skus.md) and [SAP HANA (Large Instances) storage architecture](./hana-storage-architecture.md)
+- June 10, 2020: Adding new HLI SKUs into [Available SKUs for HLI](./hana-available-skus.md) and [SAP HANA (Large Instances) storage architecture](./hana-storage-architecture.md)
