Merge pull request #229194 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/manage-apps/manage-application-permissions.md

@@ -103,7 +103,7 @@ $assignments | ForEach-Object {
 Using the following Microsoft Graph PowerShell script revokes all permissions granted to an application.
 
 ```powershell
-Connect-MgGraph -Scopes "Application.ReadWrite.All", "Directory.ReadWrite.All", "DelegatedPermissionGrant.ReadWrite.All" "AppRoleAssignment.ReadWrite.All"
+Connect-MgGraph -Scopes "Application.ReadWrite.All", "Directory.ReadWrite.All", "DelegatedPermissionGrant.ReadWrite.All", "AppRoleAssignment.ReadWrite.All"
 
 # Get Service Principal using objectId
 $sp = Get-MgServicePrincipal -ServicePrincipalID "$ServicePrincipalID"
@@ -119,7 +119,7 @@ $spOauth2PermissionsGrants |ForEach-Object {
   }
 
 # Get all application permissions for the service principal
-$spApplicationPermissions = Get-MgServicePrincipalAppRoleAssignedTo -ServicePrincipalId $Sp.Id -All | Where-Object { $_.PrincipalType -eq "ServicePrincipal" }
+$spApplicationPermissions = Get-MgServicePrincipalAppRoleAssignment -ServicePrincipalId $Sp.Id -All | Where-Object { $_.PrincipalType -eq "ServicePrincipal" }
 
 # Remove all application permissions
 $spApplicationPermissions | ForEach-Object {

articles/cosmos-db/free-tier.md

@@ -78,10 +78,11 @@ To create an account with free tier using Azure PowerShell, set the `-EnableFree
 ```powershell-interactive
 # Create a free tier account for API for NoSQL. 
 New-AzCosmosDBAccount -ResourceGroupName "MyResourcegroup" `
-    -Name "Myaccount" `
+    -Name "myaccount" `
     -ApiKind "sql" `
-    -EnableFreeTier true `
+    -EnableFreeTier $true `
     -DefaultConsistencyLevel "Session" `
+    -Location "East US" `
 ```
 
 ### Unable to create a free-tier account

articles/cosmos-db/partial-document-update-getting-started.md

@@ -225,8 +225,8 @@ key definition.
 
     const { resource: updated } = await container
         .item(
-            id = 'e379aea5-63f5-4623-9a9b-4cd9b33b91d5', 
-            partitionKeyValue = 'road-bikes'
+            'e379aea5-63f5-4623-9a9b-4cd9b33b91d5', 
+            'road-bikes'
         )
         .patch(operations);
     ```
@@ -242,8 +242,8 @@ key definition.
 
     const { resource: updated } = await container
         .item(
-            id = 'e379aea5-63f5-4623-9a9b-4cd9b33b91d5', 
-            partitionKeyValue = 'road-bikes'
+            'e379aea5-63f5-4623-9a9b-4cd9b33b91d5', 
+            'road-bikes'
         )
         .patch(operations);
     ```
@@ -260,8 +260,8 @@ key definition.
 
     const { resource: updated } = await container
         .item(
-            id = 'e379aea5-63f5-4623-9a9b-4cd9b33b91d5', 
-            partitionKeyValue = 'road-bikes'
+            'e379aea5-63f5-4623-9a9b-4cd9b33b91d5', 
+            'road-bikes'
         )
         .patch(
             body = operations,

articles/dev-box/how-to-customize-devbox-azure-image-builder.md

@@ -97,7 +97,7 @@ The next step is to use Azure VM Image Builder and Azure PowerShell to create an
     Install-Module -Name Az.ManagedServiceIdentity 
      
     # Create an identity 
-    New-AzUserAssignedIdentity -ResourceGroupName $imageResourceGroup -Name $identityName 
+    New-AzUserAssignedIdentity -ResourceGroupName $imageResourceGroup -Name $identityName -Location $location
      
     $identityNameResourceId=$(Get-AzUserAssignedIdentity -ResourceGroupName $imageResourceGroup -Name $identityName).Id 
     $identityNamePrincipalId=$(Get-AzUserAssignedIdentity -ResourceGroupName $imageResourceGroup -Name $identityName).PrincipalId
@@ -272,4 +272,4 @@ Once the compute gallery images are available in the dev center. You can use the
 
 ## Next steps
 - [Create dev box definitions](./quickstart-configure-dev-box-service.md#create-a-dev-box-definition)
-- [Configure an Azure Compute Gallery](./how-to-configure-azure-compute-gallery.md)
+- [Configure an Azure Compute Gallery](./how-to-configure-azure-compute-gallery.md)

articles/dms/howto-sql-server-to-azure-sql-powershell.md

@@ -76,10 +76,10 @@ The following example creates a service named *MyDMS* in the resource group *MyD
 
 $vSubNet = Get-AzVirtualNetworkSubnetConfig -VirtualNetwork $vNet -Name MySubnet
 
-$service = New-AzDms -ResourceGroupName myResourceGroup `
+$service = New-AzDms -ResourceGroupName MyDMSResourceGroup `
   -ServiceName MyDMS `
   -Location EastUS `
-  -Sku Basic_2vCores `  
+  -Sku GeneralPurpose_4vCores `  
   -VirtualSubnetId $vSubNet.Id`
 ```
 
@@ -105,6 +105,9 @@ $sourceConnInfo = New-AzDmsConnInfo -ServerType SQL `
   -TrustServerCertificate:$true
 ```
 
+> [!NOTE]
+> If the migration ends with an error when providing source DataSource as public IP address or the DNS of SQL Server, then use the name of the Azure VM running the SQL Server.
+
 The next example shows creation of Connection Info for a server called SQLAzureTarget using sql authentication:
 
 ```powershell
@@ -252,4 +255,4 @@ Remove-AzDms -ResourceGroupName myResourceGroup -ServiceName MyDMS
 
 ## Next step
 
-* Review the migration guidance in the Microsoft [Database Migration Guide](/data-migration/).
+* Review the migration guidance in the Microsoft [Database Migration Guide](/data-migration/).

articles/dms/pre-reqs.md

@@ -131,6 +131,7 @@ When using the Azure Database Migration Service to perform SQL Server to Azure S
 * Ensure that the service account running the source SQL Server instance has write privileges on the network share that you created and that the computer account for the source server has read/write access to the same share.
 * Make a note of a Windows user (and password) that has full control privilege on the network share that you previously created. The Azure Database Migration Service impersonates the user credential to upload the backup files to Azure Storage container for restore operation.
 * Create a blob container and retrieve its SAS URI by using the steps in the article [Manage Azure Blob Storage resources with Storage Explorer](../vs-azure-tools-storage-explorer-blobs.md#get-the-sas-for-a-blob-container). Be sure to select all permissions (Read, Write, Delete, List) on the policy window while creating the SAS URI.
+* Ensure both Azure Database Migration Service IP address and Azure SQL Managed Instance subnet can communicate with blob container.
 
    > [!NOTE]
    > For a complete listing of the prerequisites required to use the Azure Database Migration Service to perform migrations from SQL Server to SQL Managed Instance, see the tutorial [Migrate SQL Server to SQL Managed Instance](./tutorial-sql-server-to-managed-instance.md).

articles/load-testing/how-to-test-private-endpoint.md

@@ -36,9 +36,6 @@ When you start the load test, Azure Load Testing service injects the following A
 
 These resources are ephemeral and exist only during the load test run. If you restrict access to your virtual network, you need to [configure your virtual network](#configure-your-virtual-network) to enable communication between these Azure Load Testing and the injected VMs.
 
-> [!NOTE]
-> Virtual network support for Azure Load Testing is available in the following Azure regions: Australia East, East US, East US 2, North Europe, South Central US, UK South, and West US 2.
-
 ## Prerequisites
 
 - An existing virtual network and a subnet to use with Azure Load Testing.

articles/postgresql/migrate/how-to-migrate-from-oracle.md

@@ -267,9 +267,9 @@ ora2pg -t COPY -o data.sql -b %namespace/data -c %namespace/config/ora2pg.conf
 Finally, compile all files against the Azure Database for PostgreSQL server. You can choose to load the manually generated DDL files or use the second script *import_all.sh* to import those files interactively.
 
 ```
-psql -f %namespace%\schema\sequences\sequence.sql -h server1-server.postgres.database.azure.com -p 5432 -U username@server1-server -d database -l %namespace%\ schema\sequences\create_sequences.log
+psql -f %namespace%\schema\sequences\sequence.sql -h server1-server.postgres.database.azure.com -p 5432 -U username@server1-server -d database -L %namespace%\ schema\sequences\create_sequences.log
 
-psql -f %namespace%\schema\tables\table.sql -h server1-server.postgres.database.azure.com p 5432 -U username@server1-server -d database -l %namespace%\schema\tables\create_table.log
+psql -f %namespace%\schema\tables\table.sql -h server1-server.postgres.database.azure.com -p 5432 -U username@server1-server -d database -L %namespace%\schema\tables\create_table.log
 ```
 
 Here's the data import command:

articles/private-link/private-endpoint-overview.md

@@ -116,6 +116,7 @@ A private-link resource is the destination target of a specified private endpoin
 | Azure Media Services | Microsoft.Media/mediaservices | keydelivery, liveevent, streamingendpoint |
 | Resource Management Private Links | Microsoft.Authorization/resourceManagementPrivateLinks | ResourceManagement |
 | Azure Databricks | Microsoft.Databricks/workspaces | databricks_ui_api, browser_authentication |
+| Azure Monitor Private Link Scope | Microsoft.Insights/privatelinkscopes | azuremonitor |
 
 > [!NOTE]
 > You can create private endpoints only on a General Purpose v2 (GPv2) storage account.

articles/service-bus-messaging/service-bus-transactions.md

@@ -41,6 +41,10 @@ The disposition of the message (complete, abandon, dead-letter, defer) then occu
 > [!IMPORTANT]
 > Azure Service Bus doesn't retry an operation in case of an exception when the operation is in a transaction scope.
 
+## Operations that do not enlist in transaction scopes
+
+Be aware that message processing code that calls into databases and other services like Cosmos DB does not automatically enlist those downstream resources into the same transactional scope. For more information on how to handle these scenarios, look into the [guidelines on idempotent message processing](/azure/architecture/reference-architectures/containers/aks-mission-critical/mission-critical-data-platform#idempotent-message-processing).
+
 ## Transfers and "send via"
 
 To enable transactional handover of data from a queue or topic to a processor, and then to another queue or topic, Service Bus supports *transfers*. In a transfer operation, a sender first sends a message to a *transfer queue or topic*, and the transfer queue or topic immediately moves the message to the intended destination queue or topic using the same robust transfer implementation that the autoforward capability relies on. The message is never committed to the transfer queue or topic's log in a way that it becomes visible for the transfer queue or topic's consumers.