Merge pull request #263361 from MicrosoftDocs/main

1/17 11:00 AM IST Publish

Author: Saisang

articles/advisor/advisor-reference-reliability-recommendations.md

@@ -4,7 +4,7 @@ description: Full list of available reliability recommendations in Advisor.
 author: mabrahms
 ms.author: v-mabrahms
 ms.topic: article
-ms.date: 09/27/2023
+ms.date: 12/11/2023
 ---
 
 # Reliability recommendations
@@ -544,7 +544,7 @@ Learn more about [Front Door Profile - RenewExpiredBYOC (Renew the expired Azure
 
 Deploying two or more medium or large sized instances ensures business continuity during outages caused by planned or unplanned maintenance.
 
-Learn more about [Application gateway - AppGateway (Upgrade your SKU or add more instances to ensure fault tolerance)](https://aka.ms/aa_gatewayrec_learnmore).
+Learn more about [Improve the reliability of your application by using Azure Advisor - Ensure application gateway fault tolerance)](/azure/advisor/advisor-high-availability-recommendations#ensure-application-gateway-fault-tolerance).
 
 ### Avoid hostname override to ensure site integrity
 

articles/ai-studio/how-to/create-manage-compute.md

@@ -111,7 +111,6 @@ You can start or stop a compute instance from the Azure AI Studio.
 
     :::image type="content" source="../media/compute/compute-start-stop.png" alt-text="Screenshot of the option to start or stop a compute instance." lightbox="../media/compute/compute-start-stop.png":::
 
-
 ## Next steps
 
 - [Create and manage prompt flow runtimes](./create-manage-runtime.md)

articles/ai-studio/how-to/create-manage-runtime.md

@@ -147,6 +147,17 @@ Go to the page for runtime details and select **Update**. On the **Edit compute
 
 Every time you open the page for runtime details, AI Studio checks whether there are new versions of the runtime. If new versions are available, a notification appears at the top of the page. You can also manually check the latest version by selecting the **Check version** button.
 
+## Switch compute instance runtime to automatic runtime
+
+Automatic runtime has following advantages over compute instance runtime:
+- Automatic manage lifecycle of runtime and underlying compute. You don't need to manually create and managed them anymore.
+- Easily customize packages by adding packages in the `requirements.txt` file in the flow folder, instead of creating a custom environment.
+
+We would recommend you to switch to automatic runtime if you're using compute instance runtime. If you have a compute instance runtime, you can switch it to an automatic runtime (preview) by using the following steps:
+- Prepare your `requirements.txt` file in the flow folder. Make sure that you don't pin the version of `promptflow` and `promptflow-tools` in `requirements.txt`, because we already include them in the runtime base image. Packages specified in `requirements.txt` will be installed when the runtime is started. 
+- If you want to keep the automatic runtime (preview) as long running compute like compute instance, you can disable the idle shutdown toggle under automatic runtime (preview) `edit` option.
+
+
 ## Next steps
 
 - [Learn more about prompt flow](./prompt-flow.md)

articles/aks/cluster-configuration.md

@@ -12,7 +12,7 @@ As part of creating an AKS cluster, you may need to customize your cluster confi
 
 ## OS configuration
 
-AKS supports Ubuntu 22.04 as the only node operating system (OS) for clusters with Kubernetes 1.25 and higher. Ubuntu 18.04 can also be specified at node pool creation for Kubernetes versions 1.24 and below. 
+AKS supports Ubuntu 22.04 and Azure Linux 2.0 as the node operating system (OS) for clusters with Kubernetes 1.25 and higher. Ubuntu 18.04 can also be specified at node pool creation for Kubernetes versions 1.24 and below. 
 
 AKS supports Windows Server 2022 as the default operating system (OS) for Windows node pools in clusters with Kubernetes 1.25 and higher. Windows Server 2019 can also be specified at node pool creation for Kubernetes versions 1.32 and below. Windows Server 2019 is being retired after Kubernetes version 1.32 reaches end of life (EOL) and isn't supported in future releases. For more information about this retirement, see the [AKS release notes][aks-release-notes].
 

articles/aks/media/supported-kubernetes-versions/kubernetes-versions-gantt.png

@@ -32,6 +32,8 @@
 #- name: API discovery and consumption
 - name: Reference
   items:
+      - name: Azure CLI
+        href: /cli/azure/apic
       - name: REST API
         href: /rest/api/apicenter/
       - name: REST API SDKs
@@ -43,4 +45,4 @@
           - name: Python
             href: https://pypi.org/project/azure-mgmt-apicenter
       - name: Resource Manager template
-        href: /azure/templates/microsoft.apicenter/allversions
+        href: /azure/templates/microsoft.apicenter/allversions

articles/api-center/TOC.yml

@@ -155,6 +155,8 @@ Notice that the IP addresses for the gateway, control plane, appliance VM and DN
 
 Arc resource bridge may require a separate user account with the necessary roles to view and manage resources in the on-premises infrastructure (such as Arc-enabled VMware vSphere). If so, during creation of the configuration files, the `username` and `password` parameters will be required. The account credentials are then stored in a configuration file locally within the appliance VM.  
 
+> [!WARNING]
+> Arc resource bridge can only use a user account that does not have multifactor authentication enabled. 
 If the user account is set to periodically change passwords, [the credentials must be immediately updated on the resource bridge](maintenance.md#update-credentials-in-the-appliance-vm). This user account may also be set with a lockout policy to protect the on-premises infrastructure, in case the credentials aren't updated and the resource bridge makes multiple attempts to use expired credentials to access the on-premises control center.
 
 For example, with Arc-enabled VMware, Arc resource bridge needs a separate user account for vCenter with the necessary roles. If the [credentials for the user account change](troubleshoot-resource-bridge.md#insufficient-permissions), then the credentials stored in Arc resource bridge must be immediately updated by running `az arcappliance update-infracredentials` from the [management machine](#management-machine-requirements). Otherwise, the appliance will make repeated attempts to use the expired credentials to access vCenter, which will result in a lockout of the account.

articles/azure-arc/resource-bridge/system-requirements.md

@@ -11,7 +11,7 @@ ms.service: cloud-services
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: tbd
-ms.date: 12/12/2023
+ms.date: 01/16/2024
 ms.author: jejackson
 ms.custom: compute-evergreen
 ---
@@ -20,8 +20,6 @@ ms.custom: compute-evergreen
 The following tables show the Microsoft Security Response Center (MSRC) updates applied to the Azure Guest OS. Search this article to determine if a particular update applies to the Guest OS you are using. Updates always carry forward for the particular [family][family-explain] they were introduced in.
 
 ## December 2023 Guest OS
->[!NOTE]
->The December Guest OS is currently being rolled out to Cloud Service VMs that are configured for automatic updates. When the rollout is complete, this version will be made available for manual updates through the Azure portal and configuration files. The following patches are included in the December Guest OS. This list is subject to change.
 
 | Product Category | Parent KB Article | Vulnerability Description | Guest OS | Date First Introduced |
 | --- | --- | --- | --- | --- |

articles/cloud-services/cloud-services-guestos-msrc-releases.md

@@ -11,7 +11,7 @@ ms.service: cloud-services
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: tbd
-ms.date: 12/08/2023
+ms.date: 01/16/2024
 ms.author: gunnarc
 ms.custom: compute-evergreen
 ---
@@ -38,6 +38,9 @@ Unsure about how to update your Guest OS? Check [this][cloud updates] out.
 
 ## News updates
 
+###### **January 16, 2023**
+The December Guest OS has released. 
+
 ###### **December 8, 2023**
 The November Guest OS has released. 
 
@@ -239,9 +242,10 @@ The September Guest OS has released.
 
 | Configuration string | Release date | Disable date |
 | --- | --- | --- |
+|  WA-GUEST-OS-7.36_202312-01 |  January 16, 2024  |  Post 7.39  |
 |  WA-GUEST-OS-7.35_202311-01 |  December 8, 2023  |  Post 7.38  |
 |  WA-GUEST-OS-7.34_202310-01 |  October 23, 2023  |  Post 7.37  |
-|  WA-GUEST-OS-7.32_202309-01 |  September 25, 2023  |  Post 7.36  |
+|~~WA-GUEST-OS-7.32_202309-01~~|  September 25, 2023  |  Post 7.36  |
 |~~WA-GUEST-OS-7.30_202308-01~~|  August 21, 2023  |  October 23, 2023  |
 |~~WA-GUEST-OS-7.28_202307-01~~|  July 27, 2023  |  September 25, 2023  |
 |~~WA-GUEST-OS-7.27_202306-02~~|  July 8, 2023  |  August 21, 2023  |
@@ -279,9 +283,10 @@ The September Guest OS has released.
 
 | Configuration string | Release date | Disable date |
 | --- | --- | --- |
+|  WA-GUEST-OS-6.66_202312-01 |  January 16, 2024  |  Post 6.69  |
 |  WA-GUEST-OS-6.65_202311-01 |  December 8, 2023  |  Post 6.68  |
 |  WA-GUEST-OS-6.64_202310-01 |  October 23, 2023  |  Post 6.67  |
-|  WA-GUEST-OS-6.62_202309-01 |  September 25, 2023  |  Post 6.66  |
+|~~WA-GUEST-OS-6.62_202309-01~~|  September 25, 2023  |  Post 6.66  |
 |~~WA-GUEST-OS-6.61_202308-01~~|  August 21, 2023  |  October 23, 2023  |
 |~~WA-GUEST-OS-6.60_202307-01~~|  July 27, 2023  |  September 25, 2023  |
 |~~WA-GUEST-OS-6.59_202306-02~~|  July 8, 2023  |  August 21, 2023  |
@@ -353,9 +358,10 @@ The September Guest OS has released.
 
 | Configuration string | Release date | Disable date |
 | --- | --- | --- |
+|  WA-GUEST-OS-5.90_202312-01 |  January 16, 2024  |  Post 5.93  |
 |  WA-GUEST-OS-5.89_202311-01 |  December 8, 2023  |  Post 5.92  |
 |  WA-GUEST-OS-5.88_202310-01  |  October 23, 2023  |  Post 5.91  |
-|  WA-GUEST-OS-5.86_202309-01  |  September 25, 2023  |  Post 5.90  |
+|~~WA-GUEST-OS-5.86_202309-01~~|  September 25, 2023  |  Post 5.90  |
 |~~WA-GUEST-OS-5.85_202308-01~~|  August 21, 2023   |  October 23, 2023  | 
 |~~WA-GUEST-OS-5.84_202307-01~~|  July 27, 2023   |  September 25, 2023  | 
 |~~WA-GUEST-OS-5.83_202306-02~~|  July 8, 2023   |  August 21, 2023  | 
@@ -424,9 +430,10 @@ The September Guest OS has released.
 
 | Configuration string | Release date | Disable date |
 | --- | --- | --- |
+|  WA-GUEST-OS-4.126_202312-01 |  January 16, 2024  |  Post 4.129  |
 |  WA-GUEST-OS-4.125_202311-01 |  December 8, 2023  |  Post 4.128  |
 |  WA-GUEST-OS-4.124_202310-01 |  October 23, 2023  |  Post 4.127  |
-|  WA-GUEST-OS-4.122_202309-01 |  September 25, 2023  |  Post 4.126  |
+|~~WA-GUEST-OS-4.122_202309-01~~|  September 25, 2023  |  Post 4.126  |
 |~~WA-GUEST-OS-4.121_202308-01~~|  August 21, 2023  |  October 23, 2023  |
 |~~WA-GUEST-OS-4.120_202307-01~~|  July 27, 2023  |  September 25, 2023  |
 |~~WA-GUEST-OS-4.119_202306-02~~|  July 8, 2023  |  August 21, 2023  |
@@ -495,9 +502,10 @@ The September Guest OS has released.
 
 | Configuration string | Release date | Disable date |
 | --- | --- | --- |
+|  WA-GUEST-OS-3.134_202312-01 |  January 16, 2024  |  Post 3.137  |
 |  WA-GUEST-OS-3.133_202311-01 |  December 8, 2023  |  Post 3.136  |
 |  WA-GUEST-OS-3.132_202310-01  |  October 23, 2023  |  Post 3.135  |
-|  WA-GUEST-OS-3.130_202309-01  |  September 25, 2023  |  Post 3.134  |
+|~~WA-GUEST-OS-3.130_202309-01~~|  September 25, 2023  |  Post 3.134  |
 |~~WA-GUEST-OS-3.129_202308-01~~|  August 21, 2023  |  October 23, 2023  |
 |~~WA-GUEST-OS-3.128_202307-01~~|  July 27, 2023  |  September 25, 2023  |
 |~~WA-GUEST-OS-3.127_202306-02~~|  July 8, 2023  |  August 21, 2023  |
@@ -566,9 +574,10 @@ The September Guest OS has released.
 
 | Configuration string | Release date | Disable date |
 | --- | --- | --- |
+|  WA-GUEST-OS-2.146_202312-01 |  January 16, 2024  |  Post 2.149  |
 |  WA-GUEST-OS-2.145_202311-01 |  December 8, 2023  |  Post 2.148  |
 |  WA-GUEST-OS-2.144_202310-01  |  October 23, 2023  |  Post 2.146  |
-|  WA-GUEST-OS-2.142_202309-01  |  September 25, 2023  |  Post 2.144  |
+|~~WA-GUEST-OS-2.142_202309-01~~|  September 25, 2023  |  Post 2.144  |
 |~~WA-GUEST-OS-2.141_202308-01~~|  August 21, 2023  |  October 23, 2023  |
 |~~WA-GUEST-OS-2.140_202307-01~~|  July 27, 2023  |  September 25, 2023  |
 |~~WA-GUEST-OS-2.139_202306-02~~|  July 8, 2023  |  August 21, 2023  |

articles/cloud-services/cloud-services-guestos-update-matrix.md

@@ -64,7 +64,7 @@ To learn more about native Microsoft Entra join and Microsoft Entra hybrid join,
 
 Before setting up Dev Box, you need to choose the best regions for your organization. Check [Products available by region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=dev-box) and [Azure geographies](https://azure.microsoft.com/explore/global-infrastructure/geographies/#choose-your-region) to help you decide on the regions you use. If the region you prefer isn’t available for Dev Box, choose a region within 500 miles.
 
-You specify a region for your dev center and projects. Typically, these resources are in the same region as your main office or IT management center.
+Your dev center and projects typically exist in the same region as your main office or IT management center.
 
 The region of the virtual network specified in a network connection determines the region for a dev box. You can create multiple network connections based on the regions where you support developers. You can then use those connections when you're creating dev box pools to ensure that dev box users create dev boxes in a region close to them. Using a region close to the dev box user provides the best experience.