Merge pull request #204353 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: huypub

articles/active-directory-b2c/validation-technical-profile.md

@@ -86,7 +86,7 @@ Following example uses these validation technical profiles:
 ```xml
 <ValidationTechnicalProfiles>
   <ValidationTechnicalProfile ReferenceId="login-NonInteractive" ContinueOnError="false" />
-  <ValidationTechnicalProfile ReferenceId="REST-ReadProfileFromCustomertsDatabase" ContinueOnError="true" >
+  <ValidationTechnicalProfile ReferenceId="REST-ReadProfileFromCustomersDatabase" ContinueOnError="true" >
     <Preconditions>
       <Precondition Type="ClaimsExist" ExecuteActionsIf="false">
         <Value>userType</Value>

articles/active-directory/fundamentals/road-to-the-cloud-implement.md

@@ -24,9 +24,7 @@ You can enrich user attributes in Azure AD to make more user attributes availabl
 
 * App provisioning - The data source of app provisioning is Azure AD and necessary user attributes must be in there.
 
-* Application authorization - Token issued by Azure AD can include claims generated from user attributes. 
-
-* Application can make authorization decision based on the claims in token.
+* Application authorization - Token issued by Azure AD can include claims generated from user attributes so that applications can make authorization decision based on the claims in token.
 
 * Group membership population and maintenance - Dynamic groups enables dynamic population of group membership based on user attributes such as department information.
 

articles/active-directory/fundamentals/road-to-the-cloud-posture.md

@@ -34,7 +34,7 @@ The five states have exit criteria to help you determine where your environment
 
 The content then provides more detailed guidance organized to help with intentional changes to people, process, and technology to:
 
-* Establish Azure AD capabilities
+* Establish Azure AD footprint
 
 * Implement a cloud-first approach
 
@@ -101,7 +101,7 @@ In enterprise-sized organizations, IAM transformation, or even transformation fr
 
 The transformation between the states is similar to moving locations:
 
-* **Establish new location** - You purchase your destination and establish connectivity between the current location and the new location. This enables you to maintain your productivity and ability to operate. In this content, the activities are described in **[Establish Azure AD capabilities](road-to-the-cloud-establish.md)**. The results transition you to State 2.
+* **Establish new location** - You purchase your destination and establish connectivity between the current location and the new location. This enables you to maintain your productivity and ability to operate. In this content, the activities are described in **[Establish Azure AD footprint](road-to-the-cloud-establish.md)**. The results transition you to State 2.
 
 * **Limit new items in old location** - You stop investing in the old location and set policy to stage new items in new location. In this content, the activities are described in **[Implement cloud-first approach](road-to-the-cloud-implement.md)**. The activities set the foundation to migrate at scale and reach State 3.
 
@@ -122,7 +122,7 @@ As a migration of IAM to Azure AD is started, organizations must determine the p
 
 :::image type="content" source="media/road-to-cloud-posture/road-to-the-cloud-migration.png" alt-text="Table depicting three major milestones that organizations move through when implementing an AD to Azure AD migration. These include Establish Azure AD capabilities, Implement cloud-first approach, and Move workloads to the cloud." border="false":::
 
-## Establish Azure AD capabilities
+## Establish Azure AD footprint
 
 * **Initialize tenant** - Create your new Azure AD tenant that supports the vision for your end-state deployment.
 

articles/active-directory/hybrid/reference-connect-adconnectivitytools.md

@@ -14,7 +14,7 @@ ms.custom: devx-track-azurepowershell
 ---
 # Azure AD Connect:  ADConnectivityTools PowerShell Reference
 
-The following documentation provides reference information for the ADConnectivityTools.psm1 PowerShell Module that is included with Azure AD Connect.
+The following documentation provides reference information for the ADConnectivityTools PowerShell Module that is included with Azure AD Connect in `C:\Program Files\Microsoft Azure Active Directory Connect\Tools\ADConnectivityTool.psm1`.
 
 ## Confirm-DnsConnectivity
 

articles/defender-for-iot/organizations/how-to-manage-device-inventory-for-organizations.md

@@ -171,8 +171,6 @@ If you are under the impression that certain devices aren't actively communicati
 
 If you have devices no longer in use, delete them from the device inventory so that they're no longer connected to Defender for IoT.
 
-Devices must be inactive for 14 days or more in order for you to be able to delete them.
-
 **To delete a device**:
 
 In the **Device inventory** page, select the device you want to delete, and then select **Delete** :::image type="icon" source="media/how-to-manage-device-inventory-on-the-cloud/delete-device.png" border="false"::: in the toolbar at the top of the page.

articles/security/fundamentals/antimalware-code-samples.md

@@ -182,6 +182,7 @@ The code sample below shows how you can add Microsoft Antimalware for Azure Arc-
 
 ```powershell
 #Before using Azure PowerShell to manage VM extensions on your hybrid server managed by Azure Arc-enabled servers, you need to install the Az.ConnectedMachine module. Run the following command on your Azure Arc-enabled server:
+#If you have Az.ConnectedMachine installed, please make sure the version is at least 0.4.0
 install-module -Name Az.ConnectedMachine
 Import-Module -name Az.ConnectedMachine
 
@@ -192,36 +193,34 @@ $resourceGroupName = " RESOURCE GROUP NAME HERE "
 $machineName = "MACHINE NAME HERE "
 
 # Enable Antimalware with default policies
-$settingString = ‘{"AntimalwareEnabled": true}’;
+$setting = @{"AntimalwareEnabled"=$true}
 # Enable Antimalware with custom policies
-# $settingString = ‘{
-# "AntimalwareEnabled": true,
-# "RealtimeProtectionEnabled": true,
-# "ScheduledScanSettings": {
-#                             "isEnabled": true,
-#                             "day": 0,
-#                             "time": 120,
-#                             "scanType": "Quick"
-#                             },
-# "Exclusions": {
-#            "Extensions": ".ext1,.ext2",
-#                  "Paths":"",
-#                  "Processes":"sampl1e1.exe, sample2.exe"
-#             },
-# "SignatureUpdates": {
-#                               "FileSharesSources": “”,
-#                               "FallbackOrder”: “”,
-#                               "ScheduleDay": 0,
-#                               "UpdateInterval": 0,
-#                       },
-# "CloudProtection": true         
-#
-# }’;
-
+$setting2 = @{
+"AntimalwareEnabled"=$true;
+"RealtimeProtectionEnabled"=$true;
+"ScheduledScanSettings"= @{
+                            "isEnabled"=$true;
+                            "day"=0;
+                            "time"=120;
+                            "scanType"="Quick"
+                            };
+"Exclusions"= @{
+           "Extensions"=".ext1, .ext2";
+                 "Paths"="";
+                 "Processes"="sampl1e1.exe, sample2.exe"
+            };
+"SignatureUpdates"= @{
+                              "FileSharesSources"=“”;
+                              "FallbackOrder”=“”;
+                              "ScheduleDay"=0;
+                              "UpdateInterval"=0;
+                      };
+"CloudProtection"=$true
+}
 # Will be prompted to login 
 Connect-AzAccount 
 # Enable Antimalware with the policies
-New-AzConnectedMachineExtension -Name "IaaSAntimalware" -ResourceGroupName $resourceGroupName -MachineName $machineName -Location $location -SubscriptionId $subscriptionid -Publisher “Microsoft.Azure.Security” -Settings $settingString -ExtensionType “IaaSAntimalware”
+New-AzConnectedMachineExtension -Name "IaaSAntimalware" -ResourceGroupName $resourceGroupName -MachineName $machineName -Location $location -SubscriptionId $subscriptionid -Publisher “Microsoft.Azure.Security” -Settings $setting -ExtensionType “IaaSAntimalware”
 ```
 
 ## Next steps

articles/service-connector/tutorial-django-webapp-postgres-cli.md

@@ -334,7 +334,7 @@ The resource group, app name, db name are drawn from the cached values. You need
 
 ::: zone pivot="postgres-flexible-server"
 ```azurecli
-az webapp connection create postgres --client-type django
+az webapp connection create postgres-flexible --client-type django
 ```
 
 The resource group, app name, db name are drawn from the cached values. You need to provide admin password of your postgres database during the execution of this command.

articles/virtual-machines/extensions/agent-windows.md

@@ -125,7 +125,7 @@ When logged in to a Windows VM, Task Manager can be used to examine running proc
 The Azure VM Agent for Windows is automatically upgraded on images deployed from the Azure Marketplace. The new versions are stored in Azure Storage, so please ensure you don't have firewalls blocking access. As new VMs are deployed to Azure, they receive the latest VM agent at VM provision time. If you have installed the agent manually or are deploying custom VM images you will need to manually update to include the new VM agent at image creation time.
 
 ## Windows Guest Agent Automatic Logs Collection
-Windows Guest Agent has a feature to automatically collect some logs. This feature is controller by the CollectGuestLogs.exe process. 
+Windows Guest Agent has a feature to automatically collect some logs. This feature is controlled by the CollectGuestLogs.exe process. 
 It exists for both PaaS Cloud Services and IaaS Virtual Machines and its goal is to quickly & automatically collect some diagnostics logs from a VM - so they can be used for offline analysis. 
 The collected logs are Event Logs, OS Logs, Azure Logs and some registry keys. It produces a ZIP file that is transferred to the VM’s Host. This ZIP file can then be looked at by Engineering Teams and Support professionals to investigate issues on request of the customer owning the VM.
 

articles/virtual-machines/vm-naming-conventions.md

@@ -26,7 +26,7 @@ This page outlines the naming conventions used for Azure VMs. VMs use these nami
 | *Sub-family | Used for specialized VM differentiations only|
 | # of vCPUs| Denotes the number of vCPUs of the VM |
 | *Constrained vCPUs| Used for certain VM sizes only. Denotes the number of vCPUs for the [constrained vCPU capable size](./constrained-vcpu.md) |
-| Additive Features | One or more lower case letters denote additive features, such as: <br> a = AMD-based processor <br> b = Block Storage performance <br> d = diskful (i.e., a local temp disk is present); this is for newer Azure VMs, see [Ddv4 and Ddsv4-series](./ddv4-ddsv4-series.md) <br> i = isolated size <br> l = low memory; a lower amount of memory than the memory intensive size <br> m = memory intensive; the most amount of memory in a particular size <br> t = tiny memory; the smallest amount of memory in a particular size <br> s = Premium Storage capable, including possible use of [Ultra SSD](./disks-types.md#ultra-disks) (Note: some newer sizes without the attribute of s can still support Premium Storage e.g. M128, M64, etc.)<br> |
+| Additive Features | One or more lower case letters denote additive features, such as: <br> a = AMD-based processor <br> b = Block Storage performance <br> c = confidential <br> d = diskful (i.e., a local temp disk is present); this is for newer Azure VMs, see [Ddv4 and Ddsv4-series](./ddv4-ddsv4-series.md) <br> i = isolated size <br> l = low memory; a lower amount of memory than the memory intensive size <br> m = memory intensive; the most amount of memory in a particular size <br> t = tiny memory; the smallest amount of memory in a particular size <br> s = Premium Storage capable, including possible use of [Ultra SSD](./disks-types.md#ultra-disks) (Note: some newer sizes without the attribute of s can still support Premium Storage e.g. M128, M64, etc.)<br> NP = node packing <br> P = ARM Cpu <br>|
 | *Accelerator Type | Denotes the type of hardware accelerator in the specialized/GPU SKUs. Only the new specialized/GPU SKUs launched from Q3 2020 will have the hardware accelerator in the name. |
 | Version | Denotes the version of the VM Family Series |