Merge pull request #288111 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: Taojunshen

articles/azure-app-configuration/howto-import-export-data.md

@@ -14,7 +14,7 @@ ms.author: malev
 
 Azure App Configuration supports data import and export operations. Use these operations to work with configuration data in bulk and exchange data between your App Configuration store and code project. For example, you can set up one App Configuration store for testing and another one for production. You can copy application settings between them so that you don't have to enter data twice.
 
-This article provides a guide for importing and exporting data using either the [Azure portal](https://portal.azure.com) or the [Azure CLI](./scripts/cli-import.md). If you have adopted [Configuration as Code](./howto-best-practices.md#configuration-as-code) and manage your configurations in GitHub or Azure Devops, you can set up ongoing configuration file import using [GitHub Actions](./push-kv-github-action.md) or use the [Azure Pipeline Push Task](./push-kv-devops-pipeline.md).
+This article provides a guide for importing and exporting data using either the [Azure portal](https://portal.azure.com) or the [Azure CLI](./scripts/cli-import.md). If you have adopted [Configuration as Code](./howto-best-practices.md#configuration-as-code) and manage your configurations in GitHub or Azure DevOps, you can set up ongoing configuration file import using [GitHub Actions](./push-kv-github-action.md) or use the [Azure Pipeline Push Task](./push-kv-devops-pipeline.md).
 
 ## Import data
 

articles/azure-resource-manager/bicep/deployment-stacks.md

@@ -87,7 +87,7 @@ az stack group create \
   --name '<deployment-stack-name>' \
   --resource-group '<resource-group-name>' \
   --template-file '<bicep-file-name>' \
-  --action-on-unmanage 'detachAll'
+  --action-on-unmanage 'detachAll' \
   --deny-settings-mode 'none'
 ```
 

articles/azure-resource-manager/management/move-resource-group-and-subscription.md

@@ -412,27 +412,27 @@ In the request body, you specify the target resource group and the resources to
 
 ## Frequently asked questions
 
-**Question: My resource move operation, which usually takes a few minutes, has been running for almost an hour. Is there something wrong?**
+### My resource move operation, which usually takes a few minutes, has been running for almost an hour. Is there something wrong?
 
 Moving a resource is a complex operation that has different phases. It can involve more than just the resource provider of the resource you're trying to move. Because of the dependencies between resource providers, Azure Resource Manager allows 4 hours for the operation to complete. This time period gives resource providers a chance to recover from transient issues. If your move request is within the four-hour period, the operation keeps trying to complete and may still succeed. The source and destination resource groups are locked during this time to avoid consistency issues.
 
-**Question: Why is my resource group locked for four hours during resource move?**
+### Why is my resource group locked for four hours during resource move?
 
 A move request is allowed a maximum of four hours to complete. To prevent modifications on the resources being moved, both the source and destination resource groups are locked during the resource move.
 
 There are two phases in a move request. In the first phase, the resource is moved. In the second phase, notifications are sent to other resource providers that are dependent on the resource being moved. A resource group can be locked for the entire four hours when a resource provider fails either phase. During the allowed time, Resource Manager retries the failed step.
 
 If a resource can't be moved within four hours, Resource Manager unlocks both resource groups. Resources that were successfully moved are in the destination resource group. Resources that failed to move are left the source resource group.
 
-**Question: What are the implications of the source and destination resource groups being locked during the resource move?**
+### What are the implications of the source and destination resource groups being locked during the resource move?
 
 The lock prevents you from deleting either resource group, creating a new resource in either resource group, or deleting any of the resources involved in the move.
 
 The following image shows an error message from the Azure portal when a user tries to delete a resource group that is part of an ongoing move.
 
 :::image type="content" source="./media/move-resource-group-and-subscription/move-error-delete.png" alt-text="Screenshot of the Azure portal showing an error message when trying to delete a resource group involved in an ongoing move operation.":::
 
-**Question: What does the error code "MissingMoveDependentResources" mean?**
+### What does the error code "MissingMoveDependentResources" mean?
 
 When you move a resource, its dependent resources must either exist in the destination resource group or subscription, or be included in the move request. You get the MissingMoveDependentResources error code when a dependent resource doesn't meet this requirement. The error message has details about the dependent resource that needs to be included in the move request.
 
@@ -453,29 +453,29 @@ For example, moving a virtual machine could require moving seven resource types
 Another common example involves moving a virtual network. You may have to move several other resources associated with that virtual network. The move request could require moving public IP addresses, route tables, virtual network gateways, network security groups, and others.
 In general, a virtual network gateway must always be in the same resource group as its virtual network, they can't be moved separately.
 
-**Question: What does the error code "RequestDisallowedByPolicy" mean?**
+### What does the error code "RequestDisallowedByPolicy" mean?
 
 Resource Manager validates your move request before attempting the move. This validation includes checking policies defined on the resources involved in the move. For example, if you're attempting to move a key vault but your organization has a policy to deny the creation of a key vault in the target resource group, validation fails and the move is blocked. The returned error code is **RequestDisallowedByPolicy**. 
 
 For more information about policies, see [What is Azure Policy?](../../governance/policy/overview.md).
 
-**Question: Why can't I move some resources in Azure?**
+### Why can't I move some resources in Azure?
 
 Currently, not all resources in Azure support move. For a list of resources that support move, see [Move operation support for resources](move-support-resources.md).
 
-**Question: How many resources can I move in a single operation?**
+### How many resources can I move in a single operation?
 
 When possible, break large moves into separate move operations. Resource Manager immediately returns an error when there are more than 800 resources in a single operation. However, moving less than 800 resources may also fail by timing out.
 
-**Question: What is the meaning of the error that a resource isn't in succeeded state?**
+### What is the meaning of the error that a resource isn't in succeeded state?
 
 When you get an error message that indicates a resource can't be moved because it isn't in a succeeded state, it may actually be a dependent resource that is blocking the move. Typically, the error code is **MoveCannotProceedWithResourcesNotInSucceededState**.
 
 If the source or target resource group contains a virtual network, the states of all dependent resources for the virtual network are checked during the move. The check includes those resources directly and indirectly dependent on the virtual network. If any of those resources are in a failed state, the move is blocked. For example, if a virtual machine that uses the virtual network has failed, the move is blocked. The move is blocked even when the virtual machine isn't one of the resources being moved and isn't in one of the resource groups for the move.
 
 When you receive this error, you have two options. Either move your resources to a resource group that doesn't have a virtual network, or [contact support](/azure/azure-portal/supportability/how-to-create-azure-support-request).
 
-**Question: Can I move a resource group to a different subscription?**
+### Can I move a resource group to a different subscription?
 
 No, you can't move a resource group to a new subscription. But, you can move all of the resources in the resource group to a resource group in another subscription. Settings such as tags, role assignments, and policies aren't automatically transferred from the original resource group to the destination resource group. You need to reapply these settings to the new resource group. For more information, see [Move resources to new resource group or subscription](./move-support-resources.md).
 

articles/azure-resource-manager/management/move-support-resources.md

@@ -806,7 +806,7 @@ Before starting your move operation, review the [checklist](./move-resource-grou
 > [!div class="mx-tableFixed"]
 > | Resource type | Resource group | Subscription | Region move |
 > | ------------- | ----------- | ---------- | ----------- |
-> | databaseaccounts | **Yes** | **Yes** | No |
+> | databaseaccounts | **Yes** | No | No |
 
 ## Microsoft.DomainRegistration
 

articles/azure-resource-manager/templates/template-tutorial-create-first-template.md

@@ -120,8 +120,6 @@ When you deploy a template, you can specify a resource group to contain the reso
 > [!NOTE]
 > Samples for the Azure CLI are written for the bash shell. To run this sample in Windows PowerShell or the Command Prompt, you may need to remove the back slashes and write the command as one line such as:
 
-```az group create --name myResourceGroup --location "Central US"```
-
 # [PowerShell](#tab/azure-powershell)
 
 ```azurepowershell

articles/storage/blobs/lifecycle-management-overview.md

@@ -186,7 +186,7 @@ The run conditions are based on age. Current versions use the last modified time
 
 ## Lifecycle policy runs
 
-When you configure or edit a lifecycle policy., it can take up to 24 hours for changes to go into effect and for the first execution to start. The time taken for policy actions to complete depends on the number of blobs evaluated and operated on.
+When you configure or edit a lifecycle policy, it can take up to 24 hours for changes to go into effect and for the first execution to start. The time taken for policy actions to complete depends on the number of blobs evaluated and operated on.
 
 If you disable a policy, then no new policy runs will be scheduled, but if a run is already in progress, that run will continue until it completes and you're billed for any actions that are required to complete the run. See [Regional availability and pricing](#regional-availability-and-pricing).  
 

articles/storage/blobs/storage-blob-change-feed.md

@@ -14,7 +14,7 @@ ms.custom: engagement-fy23
 
 # Change feed support in Azure Blob Storage
 
-The purpose of the change feed is to provide transaction logs of all the changes that occur to the blobs and the blob metadata in your storage account. The change feed provides **ordered**, **guaranteed**, **durable**, **immutable**, **read-only** log of these changes. Client applications can read these logs at any time, either in streaming or in batch mode. Each change generates exactly one transaction log entry, so you won't have to manage multiple log entries for the same change. The change feed enables you to build efficient and scalable solutions that process change events that occur in your Blob Storage account at a low cost.
+The purpose of the change feed is to provide transaction logs of all the changes that occur to the blobs and the blob metadata in your storage account. The change feed provides **ordered**, **guaranteed**, **durable**, **immutable**, **read-only** logs of these changes. Client applications can read these logs at any time, either in streaming or in batch mode. Each change generates exactly one transaction log entry, so you won't have to manage multiple log entries for the same change. The change feed enables you to build efficient and scalable solutions that process change events that occur in your Blob Storage account at a low cost.
 
 To learn how to process records in the change feed, see [Process change feed in Azure Blob Storage](storage-blob-change-feed-how-to.md).