Merge pull request #260342 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/aks/developer-best-practices-resource-management.md

@@ -31,7 +31,7 @@ Use pod requests and limits to manage compute resources within an AKS cluster. P
 
 *Pod requests* define a set amount of CPU and memory the pod needs regularly.
 
-In your pod specifications, it's important you define these requests and limits based on the above information. If you don't include these values, the Kubernetes scheduler can't consider the resources your applications requires to help with scheduling decisions.
+In your pod specifications, it's important you define these requests and limits based on the above information. If you don't include these values, the Kubernetes scheduler can't consider the resources your applications require to help with scheduling decisions.
 
 Monitor the performance of your application to adjust pod requests. If you underestimate pod requests, your application may receive degraded performance due to over-scheduling a node. If requests are overestimated, your application may have increased scheduling difficulty.
 
@@ -47,7 +47,7 @@ Monitor the performance of your application at different times during the day or
 
 > [!IMPORTANT]
 >
-> In your pod specifications, define these requests and limits based on the above information. Failing to include these values prevents the Kubernetes scheduler from accounting for resources your applications requires to help with scheduling decisions.
+> In your pod specifications, define these requests and limits based on the above information. Failing to include these values prevents the Kubernetes scheduler from accounting for resources your applications require to help with scheduling decisions.
 
 If the scheduler places a pod on a node with insufficient resources, application performance is degraded. Cluster administrators **must set *resource quotas*** on a namespace that requires you to set resource requests and limits. For more information, see [resource quotas on AKS clusters][resource-quotas].
 

articles/azure-monitor/containers/container-insights-enable-aks.md

@@ -124,13 +124,13 @@ az aks enable-addons -a monitoring -n <cluster-name> -g <cluster-resource-group-
 1.	Download Bicep templates and parameter files depending on whether you want to enable Syslog collection.
 
     **Syslog**
-    - Template file: [Template without Syslog](https://aka.ms/enable-monitoring-msi-bicep-template)
-    - Parameter file: [Parameter without Syslog](https://aka.ms/enable-monitoring-msi-bicep-parameters)
-
-    **No Syslog**
     - Template file: [Template with Syslog](https://aka.ms/enable-monitoring-msi-syslog-bicep-template)
     - Parameter file: [Parameter with Syslog](https://aka.ms/enable-monitoring-msi-syslog-bicep-parameters)
 
+    **No Syslog**
+    - Template file: [Template without Syslog](https://aka.ms/enable-monitoring-msi-bicep-template)
+    - Parameter file: [Parameter without Syslog](https://aka.ms/enable-monitoring-msi-bicep-parameters)
+
 2.	Edit the following values in the parameter file:
 
     | Parameter | Description |

articles/container-apps/get-started.md

@@ -100,12 +100,16 @@ az provider register --namespace Microsoft.OperationalInsights
 
 Now that your Azure CLI setup is complete, you can define the environment variables that are used throughout this article.
 
+## Create a resource group
+
+```azurepowershell
+az group create --location centralus --resource-group name my-container-apps
+```
 
 ## Create and deploy the container app
 
 Create and deploy your first container app with the `containerapp up` command. This command will:
 
-- Create the resource group
 - Create the Container Apps environment
 - Create the Log Analytics workspace
 - Create and deploy the container app using a public container image

articles/service-health/resource-health-checks-resource-types.md

@@ -264,7 +264,7 @@ Below is a complete list of all the checks executed through resource health by r
 ## Microsoft.SQL/servers/databases
 |Executed Checks|
 |---|
-| - Have login attempts to the database failed because the database was unavailable?|
+| - When there are many logins, have more than a quarter of the login attempts failed for system reasons?<br> - Have more that one login attempt failed for system reasons (in two of the last three minutes)?|
 
 ## Microsoft.Storage/storageAccounts
 |Executed Checks|

articles/synapse-analytics/sql-data-warehouse/backup-and-restore.md

@@ -41,6 +41,8 @@ from     sys.pdw_loader_backup_runs
 order by run_id desc
 ;
 ```
+> [!NOTE]
+> Backups occur every four (4) hours to meet an eight (8) hour SLA. Therefore, the sys.pdw_loader_backup_runs dynamic management view will display backup activity every four (4) hours.
 
 ## User-Defined Restore Points
 
@@ -130,4 +132,4 @@ You can [submit a support ticket](sql-data-warehouse-get-started-create-support-
 
 ## Next steps
 
-For more information about restore points, see [User-defined restore points](sql-data-warehouse-restore-points.md)
+For more information about restore points, see [User-defined restore points](sql-data-warehouse-restore-points.md)

articles/virtual-machines/windows-in-place-upgrade.md

@@ -57,7 +57,7 @@ To start an in-place upgrade the upgrade media must be attached to the VM as a M
 | diskName | Name of the Managed Disk that will contain the upgrade media |
 | sku | Windows Server upgrade media version. This must be either:  `server2016Upgrade` or `server2019Upgrade` or `server2022Upgrade` or `server2012Upgrade` |
 
-If you have more than one subscription, you should run `Set-AzsSubscription -SubscriptionId <String>` to specify which subscription to use.
+If you have more than one subscription, you should run `Set-AzContext -Subscription '<subscription name or id>` to specify which subscription to use.
 
 ### PowerShell script