Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-rbac-transfer-sub-synapse-analytics-workspace

Author: rolyon

articles/aks/TOC.yml

@@ -751,4 +751,8 @@
     - name: FAQ
       href: faq.md
 - name: Support and troubleshooting
-  href: aks-support-help.md
+  items:
+    - name: Support options for AKS
+      href: aks-support-help.md
+    - name: Troubleshooting documentation for AKS
+      href: /troubleshoot/azure/azure-kubernetes/welcome-azure-kubernetes

articles/aks/aks-support-help.md

@@ -1,30 +1,28 @@
 ---
-title: Azure Kubernetes Service support and help options 
-description: How to obtain help and support for questions or problems when you create solutions using Azure Kubernetes Service. 
+title: Support and troubleshooting for Azure Kubernetes Service (AKS)
+description: This article provides support and troubleshooting options for Azure Kubernetes Service (AKS).
 ms.topic: troubleshooting
-ms.date: 10/18/2022
+ms.date: 09/27/2023
 ms.custom: support-help-page
 ---
 
 # Support and troubleshooting for Azure Kubernetes Service (AKS)
 
-Here are suggestions for where you can get help when developing your Azure Kubernetes Service (AKS) solutions.
-
 ## Self help troubleshooting
 
 :::image type="icon" source="./media/logos/doc-logo.png" alt-text="":::
 
-Various articles explain how to determine, diagnose, and fix issues that you might encounter when using Azure Kubernetes Service. Use these articles to troubleshoot deployment failures, security-related problems, connection issues and more.
-
-For a full list of self help troubleshooting content, see [Azure Kubernetes Service troubleshooting documentation](/troubleshoot/azure/azure-kubernetes/welcome-azure-kubernetes)
+The [AKS troubleshooting documentation](/troubleshoot/azure/azure-kubernetes/welcome-azure-kubernetes) provides guidance for how to diagnose and resolve issues that you might encounter when using AKS. These articles cover how to troubleshoot deployment failures, security-related problems, connection issues, and more.
 
 ## Post a question on Microsoft Q&A
 
 :::image type="icon" source="./media/logos/microsoft-logo.png" alt-text="":::
 
-For quick and reliable answers on your technical product questions from Microsoft Engineers, Azure Most Valuable Professionals (MVPs), or our expert community, engage with us on [Microsoft Q&A](/answers/products/azure), Azure's preferred destination for community support.
+Azure's preferred destination for community support, [Microsoft Q&A](/answers/products/azure), allows you to ask technical questions and engage with Azure engineers, Most Valuable Professionals (MVPs), partners, and customers. When you ask a question, make sure you use the `azure-kubernetes-service` tag. You can also submit your own answers and help other community members with their questions.
+
+If you can't find an answer to your problem using search, you can submit a new question to Microsoft Q&A and tag it with the appropriate Azure service and area.
 
-If you can't find an answer to your problem using search, submit a new question to Microsoft Q&A. Use one of the following tags when asking your question:
+The following table lists the tags for AKS and related services:
 
 | Area | Tag |
 |-------|----------------------|
@@ -44,37 +42,35 @@ If you can't find an answer to your problem using search, submit a new question
 
 :::image type="icon" source="./media/logos/azure-logo.png" alt-text="":::
 
-Explore the range of [Azure support options and choose the plan](https://azure.microsoft.com/support/plans) that best fits, whether you're a developer just starting your cloud journey or a large organization deploying business-critical, strategic applications. Azure customers can create and manage support requests in the Azure portal.
+Explore the range of [Azure support options](https://azure.microsoft.com/support/plans) and choose a plan that best fits your needs. Azure customers can create and manage support requests in the Azure portal.
 
-- If you already have an Azure Support Plan, [open a support request here](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).
-
-- To sign up for a new Azure Support Plan, [compare support plans](https://azure.microsoft.com/support/plans/) and select the plan that works for you.
+If you already have an Azure Support Plan, you can [open a support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).
 
 ## Create a GitHub issue
 
 :::image type="icon" source="./media/logos/github-logo.png" alt-text="":::
 
-If you need help with the language and tools used to develop and manage Azure Kubernetes Service, open an issue in its repository on GitHub.
+If you need help with the languages and tools for developing and managing AKS, you can open an issue in its GitHub repository.
+
+The following table lists the GitHub repositories for AKS and related services:
 
 | Library | GitHub issues URL|
 | --- | --- |
 | Azure PowerShell | https://github.com/Azure/azure-powershell/issues |
-| Azure CLI | https://github.com/Azure/azure-cli/issues | 
-| Azure REST API | https://github.com/Azure/azure-rest-api-specs/issues | 
-| Azure SDK for Java | https://github.com/Azure/azure-sdk-for-java/issues | 
-| Azure SDK for Python | https://github.com/Azure/azure-sdk-for-python/issues | 
-| Azure SDK for .NET | https://github.com/Azure/azure-sdk-for-net/issues | 
-| Azure SDK for JavaScript | https://github.com/Azure/azure-sdk-for-js/issues | 
-| Terraform | https://github.com/Azure/terraform/issues | 
+| Azure CLI | https://github.com/Azure/azure-cli/issues |
+| Azure REST API | https://github.com/Azure/azure-rest-api-specs/issues |
+| Azure SDK for Java | https://github.com/Azure/azure-sdk-for-java/issues |
+| Azure SDK for Python | https://github.com/Azure/azure-sdk-for-python/issues |
+| Azure SDK for .NET | https://github.com/Azure/azure-sdk-for-net/issues |
+| Azure SDK for JavaScript | https://github.com/Azure/azure-sdk-for-js/issues |
+| Terraform | https://github.com/Azure/terraform/issues |
 
 ## Stay informed of updates and new releases
 
 :::image type="icon" source="./media/logos/updates-logo.png" alt-text="":::
 
-Learn about important product updates, roadmap, and announcements in [Azure Updates](https://azure.microsoft.com/updates/?category=compute).
-
-News and information about Azure Virtual Machines is shared at the [Azure blog](https://azure.microsoft.com/blog/topics/virtual-machines/).
+Learn about important product updates, roadmap, and announcements in [Azure Updates](https://azure.microsoft.com/updates/?category=compute). For information about Azure Virtual Machines, see the [Azure blog](https://azure.microsoft.com/blog/topics/virtual-machines/).
 
 ## Next steps
 
-Learn more about [Azure Kubernetes Service](./index.yml)
+Visit the [Azure Kubernetes Service (AKS) documentation](./index.yml).

articles/aks/keda-integrations.md

@@ -3,18 +3,18 @@ title: Integrations with Kubernetes Event-driven Autoscaling (KEDA) on Azure Kub
 description: Integrations with Kubernetes Event-driven Autoscaling (KEDA) on Azure Kubernetes Service (AKS) (Preview).
 author: tomkerkhove
 ms.topic: article
-ms.date: 05/24/2022
+ms.date: 09/27/2023
 ms.author: tomkerkhove
 ---
 
 # Integrations with Kubernetes Event-driven Autoscaling (KEDA) on Azure Kubernetes Service (AKS) (Preview)
 
-The Kubernetes Event-driven Autoscaling (KEDA) add-on integrates with features provided by Azure and open source projects.
+The Kubernetes Event-driven Autoscaling (KEDA) add-on for AKS integrates with features provided by Azure and open-source projects.
 
 [!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
 
 > [!IMPORTANT]
-> Integrations with open source projects are not covered by the [AKS support policy][aks-support-policy].
+> The [AKS support policy][aks-support-policy] doesn't cover integrations with open-source projects.
 
 ## Observe your autoscaling with Kubernetes events
 
@@ -24,9 +24,9 @@ To learn about the available metrics, we recommend reading the [KEDA documentati
 
 ## Scalers for Azure services
 
-KEDA can integrate with various tools and services through [a rich catalog of 50+ KEDA scalers][keda-scalers]. It supports leading cloud platforms (such as Azure) and open-source technologies such as Redis and Kafka.
+KEDA integrates with various tools and services through [a rich catalog of 50+ KEDA scalers][keda-scalers] and supports leading cloud platforms and open-source technologies.
 
-It leverages the following scalers for Azure services:
+KEDA leverages the following scalers for Azure services:
 
 - [Azure Application Insights](https://keda.sh/docs/latest/scalers/azure-app-insights/)
 - [Azure Blob Storage](https://keda.sh/docs/latest/scalers/azure-storage-blob/)
@@ -38,18 +38,18 @@ It leverages the following scalers for Azure services:
 - [Azure Service Bus](https://keda.sh/docs/latest/scalers/azure-service-bus/)
 - [Azure Storage Queue](https://keda.sh/docs/latest/scalers/azure-storage-queue/)
 
-Next to the built-in scalers, you can install external scalers yourself to autoscale on other Azure services:
+You can also install external scalers to autoscale on other Azure services:
 
 - [Azure Cosmos DB (Change feed)](https://github.com/kedacore/external-scaler-azure-cosmos-db)
 
-However, these external scalers aren't supported as part of the add-on and rely on community support.
+These external scalers *aren't supported as part of the add-on* and rely on community support.
 
 ## Next steps
 
-* [Enable the KEDA add-on with an ARM template][keda-arm]
-* [Enable the KEDA add-on with the Azure CLI][keda-cli]
-* [Troubleshoot KEDA add-on problems][keda-troubleshoot]
-* [Autoscale a .NET Core worker processing Azure Service Bus Queue message][keda-sample]
+- [Enable the KEDA add-on with an ARM template][keda-arm]
+- [Enable the KEDA add-on with the Azure CLI][keda-cli]
+- [Troubleshoot KEDA add-on problems][keda-troubleshoot]
+- [Autoscale a .NET Core worker processing Azure Service Bus Queue message][keda-sample]
 
 <!-- LINKS - internal -->
 [aks-support-policy]: support-policies.md

articles/container-instances/container-instances-log-analytics.md

@@ -18,9 +18,6 @@ The following sections describe how to create a logging-enabled container group
 
 [!INCLUDE [azure-monitor-log-analytics-rebrand](../../includes/azure-monitor-log-analytics-rebrand.md)]
 
-> [!NOTE]
-> Currently, you can only send event data from Linux container instances to Log Analytics.
-
 ## Prerequisites
 
 To enable logging in your container instances, you need the following:

articles/healthcare-apis/fhir/migration-strategies.md

@@ -34,9 +34,9 @@ To migrate your data, follow these steps:
 Compare the differences between Azure API for FHIR and Azure Health Data Services. Also review your architecture and assess if any changes need to be made.
 
 |Capabilities|Azure API for FHIR|Azure Health Data Services|
-|----------------|----------------------|------------------|
+|------------|------------------|--------------------------|
 |**Settings**|Supported: <br> • Local RBAC <br> • SMART on FHIR Proxy|Planned deprecation: <br> • Local RBAC (9/6/23) <br> • SMART on FHIR Proxy (9/21/26)|
-|**Data storage Volume**|More than 4 TB|Current support is 4 TB (Reach out to the CSS team if you need more than 4 TB)|
+|**Data storage Volume**|More than 4 TB|Current support is 4 TB (Open an [Azure support request](../../azure-portal/supportability/how-to-create-azure-support-request.md) if you need more than 4 TB)|
 |**Data ingress**|Tools available in OSS|$import operation|
 |**Autoscaling**|Supported on request and incurs charge|Enabled by default at no extra charge|
 |**Search parameters**|Bundle type supported: Batch <br> • Include and revinclude, iterate modifier not supported  <br> • Sorting supported by first name, last name, birthdate and clinical date|Bundle type supported: Batch and transaction  <br> • Selectable search parameters  <br> • Include, revinclude, and iterate modifier is supported <br>• Sorting supported by string and dateTime fields|

articles/machine-learning/how-to-deploy-custom-container.md

@@ -116,43 +116,11 @@ You can configure your cloud deployment using YAML. Take a look at the sample YA
 
 __tfserving-endpoint.yml__
 
-```yml
-$schema: https://azuremlsdk2.blob.core.windows.net/latest/managedOnlineEndpoint.schema.json
-name: tfserving-endpoint
-auth_mode: aml_token
-```
+:::code language="yaml" source="~/azureml-examples-main/cli/endpoints/online/custom-container/tfserving/half-plus-two/tfserving-endpoint.yml":::
 
 __tfserving-deployment.yml__
 
-```yml
-$schema: https://azuremlschemas.azureedge.net/latest/managedOnlineDeployment.schema.json
-name: tfserving-deployment
-endpoint_name: tfserving-endpoint
-model:
-  name: tfserving-mounted
-  version: {{MODEL_VERSION}}
-  path: ./half_plus_two
-environment_variables:
-  MODEL_BASE_PATH: /var/azureml-app/azureml-models/tfserving-mounted/{{MODEL_VERSION}}
-  MODEL_NAME: half_plus_two
-environment:
-  #name: tfserving
-  #version: 1
-  image: docker.io/tensorflow/serving:latest
-  inference_config:
-    liveness_route:
-      port: 8501
-      path: /v1/models/half_plus_two
-    readiness_route:
-      port: 8501
-      path: /v1/models/half_plus_two
-    scoring_route:
-      port: 8501
-      path: /v1/models/half_plus_two:predict
-instance_type: Standard_DS3_v2
-instance_count: 1
-```
-
+:::code language="yaml" source="~/azureml-examples-main/cli/endpoints/online/custom-container//tfserving/half-plus-two/tfserving-deployment.yml":::
 
 # [Python SDK](#tab/python)
 

articles/virtual-machines/maintenance-configurations.md

@@ -60,13 +60,15 @@ This scope is integrated with [Update Manager](../update-center/overview.md), wh
 - A minimum of 1 hour and 30 minutes is required for the maintenance window.
 - The value of **Repeat** should be at least 6 hours.
 
+In rare cases if platform catchup host update window happens to coincide with the guest (VM) patching window and if the guest patching window don't get sufficient time to execute after host update then the system would show **Schedule timeout, waiting for an ongoing update to complete the resource** error since only a single update is allowed by the platform at a time. 
+
 >[!IMPORTANT]
 > The minimum maintenance window has been increased from 1 hour 10 minutes to 1 hour 30 minutes, while the minimum repeat value has been set to 6 hours for new schedules. **Please note that your existing schedules will not get impacted; however, we strongly recommend updating existing schedules to include these new changes.**
 
 To learn more about this topic, checkout [Update Manager and scheduled patching](../update-center/scheduled-patching.md)
 
 > [!NOTE]
-> In rare cases if platform catchup host update window happens to coincide with the guest (VM) patching window and if the guest patching window don't get sufficient time to execute after host update then the system would show **Schedule timeout, waiting for an ongoing update to complete the resource** error since only a single update is allowed by the platform at a time. 
+> If you move a VM to a different resource group or subscription, the scheduled patching for the VM stops working as this scenario is currently unsupported by the system.
 
 ## Shut Down Machines