Merge branch 'main' into release-aio-m2

Author: v-alje

CODEOWNERS

@@ -2,19 +2,19 @@
 # Each line is a file pattern followed by one or more owners.
 
 # Folder paths in this list have been migrated to new repositories and content can no longer be created for these services in this repo.
-/articles/aks @tynevi @thomps23
-/articles/defender-for-cloud  @tynevi @thomps23
-/articles/attestation  @tynevi @thomps23
-/articles/confidential-ledger  @tynevi @thomps23
-/articles/dedicated-hsm  @tynevi @thomps23
-/articles/key-vault  @tynevi @thomps23
-/articles/payment-hsm  @tynevi @thomps23
-/articles/postgresql @tynevi @thomps23
-/articles/cosmos-db @tynevi @thomps23
-/articles/dms @tynevi @thomps23
-/articles/mariadb @tynevi @thomps23
-/articles/mysql @tynevi @thomps23
-/articles/managed-instance-apache-cassandra @tynevi @thomps23
+/articles/aks @tynevi @thomps23 @jasonwhowell
+/articles/defender-for-cloud  @tynevi @thomps23 @jasonwhowell
+/articles/attestation  @tynevi @thomps23 @jasonwhowell
+/articles/confidential-ledger  @tynevi @thomps23 @jasonwhowell
+/articles/dedicated-hsm  @tynevi @thomps23 @jasonwhowell
+/articles/key-vault  @tynevi @thomps23 @jasonwhowell
+/articles/payment-hsm  @tynevi @thomps23 @jasonwhowell
+/articles/postgresql @tynevi @thomps23 @jasonwhowell
+/articles/cosmos-db @tynevi @thomps23 @jasonwhowell
+/articles/dms @tynevi @thomps23 @jasonwhowell
+/articles/mariadb @tynevi @thomps23 @jasonwhowell
+/articles/mysql @tynevi @thomps23 @jasonwhowell
+/articles/managed-instance-apache-cassandra @tynevi @thomps23 @jasonwhowell
 /articles/virtual-machines @jasonwhowell @thomps23
 /articles/virtual-machines-scale-sets @jasonwhowell @thomps23
 /articles/container-instances @jasonwhowell @thomps23

articles/app-service/includes/tutorial-connect-msi-azure-database/code-postgres-mi.md

@@ -109,6 +109,11 @@ For more information, see the following resources:
     conn = psycopg2.connect(conn_string + ' password=' + accessToken.token) 
     ```
 
+For more information, see the following resources:
+
+* [Create and deploy a Flask Python web app to Azure with system-assigned managed identity](/azure/developer/python/tutorial-python-managed-identity-cli)
+* [Create and deploy a Django web app to Azure with a user-assigned managed identity](/azure/developer/python/tutorial-python-managed-identity-user-assigned-cli)
+
 # [NodeJS](#tab/nodejs-postgres-mi)
 
 1. Install dependencies.

articles/app-service/toc.yml

@@ -206,6 +206,8 @@
                   href: tutorial-connect-msi-sql-database.md
                 - name: Connect Java Tomcat to Postgres
                   href: tutorial-java-tomcat-connect-managed-identity-postgresql-database.md
+                - name: Connect Python Flask app to Postgres
+                  href: /azure/developer/python/tutorial-python-managed-identity-cli?toc=/azure/app-service/toc.json&bc=/azure/bread/toc.json
             - name: Connect to Microsoft Graph with managed identity
               items: 
                 - name: Use .NET

articles/azure-functions/functions-scenarios.md

@@ -2,9 +2,14 @@
 title: Azure Functions Scenarios 
 description: Identify key scenarios that use Azure Functions to provide serverless compute resources in aa Azure cloud-based topology. 
 ms.topic: conceptual
-ms.custom: devx-track-extended-java, devx-track-js, devx-track-python
-ms.date: 05/15/2023
-zone_pivot_groups: programming-languages-set-functions-lang-workers
+ms.custom: 
+  - devx-track-extended-java
+  - devx-track-js
+  - devx-track-python
+ms.collection: 
+  - ce-skilling-ai-copilot
+ms.date: 07/25/2024
+zone_pivot_groups: programming-languages-set-functions
 ---
 
 # Azure Functions scenarios
@@ -152,6 +157,7 @@ A function might also call a TensorFlow model or Azure AI services to process an
 
 ::: zone pivot="programming-language-csharp"  
 + Tutorial: [Text completion using Azure OpenAI](functions-add-openai-text-completion.md?pivots=programming-language-csharp)
++ Sample: [Upload text files and access data using various OpenAI features](https://github.com/azure-samples/azure-functions-openai-demo) 
 + Sample: [Text summarization using AI Cognitive Language Service](https://github.com/Azure-Samples/function-csharp-ai-textsummarize)
 + Sample: [Text completion using Azure OpenAI](https://github.com/Azure/azure-functions-openai-extension/tree/main/samples/textcompletion/csharp-ooproc)
 + Sample: [Provide assistant skills to your model](https://github.com/Azure/azure-functions-openai-extension/tree/main/samples/assistant/csharp-ooproc)
@@ -169,6 +175,13 @@ A function might also call a TensorFlow model or Azure AI services to process an
 + Tutorial: [Text completion using Azure OpenAI](functions-add-openai-text-completion.md?pivots=programming-language-javascript)
 + Training: [Create a custom skill for Azure AI Search](/training/modules/create-enrichment-pipeline-azure-cognitive-search)
 + Sample: [Chat using ChatGPT](https://github.com/Azure-Samples/function-javascript-ai-openai-chatgpt)
++ Sample: [Upload text files and access data using various OpenAI features](https://github.com/azure-samples/azure-functions-openai-demo)
+::: zone-end
+::: zone pivot="programming-language-typescript"  
++ Tutorial: [Text completion using Azure OpenAI](functions-add-openai-text-completion.md?pivots=programming-language-typescript)
++ Training: [Create a custom skill for Azure AI Search](/training/modules/create-enrichment-pipeline-azure-cognitive-search)
++ Sample: [Chat using ChatGPT](https://github.com/Azure-Samples/function-javascript-ai-openai-chatgpt)
++ Sample: [Upload text files and access data using various OpenAI features](https://github.com/azure-samples/azure-functions-openai-demo)
 ::: zone-end  
 ::: zone pivot="programming-language-python"  
 + Tutorial: [Text completion using Azure OpenAI](functions-add-openai-text-completion.md?pivots=programming-language-python)

articles/azure-netapp-files/cool-access-introduction.md

@@ -16,13 +16,16 @@ Using Azure NetApp Files storage with cool access, you can configure inactive da
 
 Most cold data is associated with unstructured data. It can account for more than 50% of the total storage capacity in many storage environments. Infrequently accessed data associated with productivity software, completed projects, and old datasets are an inefficient use of a high-performance storage. 
 
-Azure NetApp Files supports cool access with three [service levels](azure-netapp-files-service-levels.md) (Standard, Premium and Ultra).
+Azure NetApp Files supports cool access with three [service levels](azure-netapp-files-service-levels.md) (Standard, Premium, and Ultra).
 
 The following diagram illustrates an application with a volume enabled for cool access.
 
 :::image type="content" source="./media/cool-access-introduction/cool-access-explainer.png" alt-text="Diagram of cool access tiering showing cool volumes being moved to the cool tier." lightbox="./media/cool-access-introduction/cool-access-explainer.png" border="false":::
 
-In the initial write, data blocks are assigned a "warm" temperature value (in the diagram, red data blocks) and exist on the "hot" tier. As the data resides on the volume, a temperature scan monitors the activity of each block. When a data block is inactive, the temperature scan decreases the value of the block until it has been inactive for the number of days specified in the cooling period. The cooling period can be between 2 and 183 days; it has a default value of 31 days. Once marked "cold,"  the tiering scan collects blocks and packages them into 4-MB objects, which are moved to Azure storage fully transparently. To the application and users, those cool blocks still appear online. Tiered data appears to be online and continues to be available to users and applications by transparent and automated retrieval from the cool tier.
+In the initial write, data blocks are assigned a "warm" temperature value (in the diagram, red data blocks) and exist on the "hot" tier. As the data resides on the volume, a temperature scan monitors the activity of each block. When a data block is inactive, the temperature scan decreases the value of the block until it has been inactive for the number of days specified in the coolness period. The coolness period can be between 2 and 183 days; it has a default value of 31 days. Once marked "cold," the tiering scan collects blocks and packages them into 4-MB objects, which are moved to Azure storage fully transparently. To the application and users, those cool blocks still appear online. Tiered data appears to be online and continues to be available to users and applications by transparent and automated retrieval from the cool tier.
+
+>[!NOTE]
+>When you enable cool access, data that satisfies the conditions set by the coolness period moves to the cool tier. For example, if the coolness period is set to 30 days, any data that has been cool for at least 30 days moves to the cool tier _when_ you enable cool access. 
 
 By `Default` (unless cool access retrieval policy is configured otherwise), data blocks on the cool tier that are read randomly again become "warm" and are moved back to the hot tier. Once marked as _warm_, the data blocks are again subjected to the temperature scan. However, large sequential reads (such as index and antivirus scans) on inactive data in the cool tier don't "warm" the data nor do they trigger inactive data to be moved back to the hot tier.
 
@@ -99,7 +102,7 @@ Billing calculation for a capacity pool is at the hot-tier rate for the data tha
 
 ### Examples of billing structure
 
-Assume that you created a 4 TiB Standard capacity pool. The billing structure is at the Standard capacity tier rate for the entire 4 TiB. 
+Assume that you created a 4-TiB Standard capacity pool. The billing structure is at the Standard capacity tier rate for the entire 4 TiB. 
 
 When you create volumes in the capacity pool and start tiering data to the cool tier, the following scenarios explain the applicable billing structure: 
 

articles/azure-netapp-files/manage-cool-access.md

@@ -22,6 +22,7 @@ The storage with cool access feature provides options for the “coolness period
 * No guarantee is provided for any maximum latency for client workload for any of the service tiers. 
 * Although cool access is available for the Standard, Premium, and Ultra service levels, how you're billed for using the feature differs from the hot tier service level charges. See the [Billing section](cool-access-introduction.md#billing) for details and examples. 
 * You can convert an existing capacity pool into a cool-access capacity pool to create cool access volumes. However, once the capacity pool is enabled for cool access, you can't convert it back to a non-cool-access capacity pool.  
+    * When you enable cool access, data that satisfies the conditions set by the coolness period moves to the cool tier. For example, if the coolness period is set to 30 days, any data that has been cool for at least 30 days moves to the cool tier _when_ you enable cool access. 
 * A cool-access capacity pool can contain both volumes with cool access enabled and volumes with cool access disabled.
 * To prevent data retrieval from the cool tier to the hot tier during sequential read operations (for example, antivirus or other file scanning operations), set the cool access retrieval policy to "Default" or "Never." For more information, see [Enable cool access on a new volume](#enable-cool-access-on-a-new-volume).
 * After the capacity pool is configured with the option to support cool access volumes, the setting can't be disabled at the _capacity pool_ level. However, you can turn on or turn off the cool access setting at the volume level anytime. Turning off the cool access setting at the _volume_ level stops further tiering of data.  

articles/azure-resource-manager/bicep/add-template-to-azure-pipelines.md

@@ -3,7 +3,7 @@ title: CI/CD with Azure Pipelines, Bicep, and bicepparam files
 description: In this quickstart, you learn how to configure continuous integration in Azure Pipelines by using Bicep and bicepparam files. It shows how to use an Azure CLI task to deploy a bicepparam file.
 ms.topic: quickstart
 ms.custom: devx-track-bicep, devx-track-azurecli
-ms.date: 02/29/2024
+ms.date: 09/26/2024
 ---
 
 # Quickstart: Integrate Bicep with Azure Pipelines

articles/azure-resource-manager/bicep/child-resource-name-type.md

@@ -3,7 +3,7 @@ title: Child resources in Bicep
 description: Describes how to set the name and type for child resources in Bicep.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 06/23/2023
+ms.date: 09/26/2024
 ---
 
 # Set name and type for child resources in Bicep

articles/azure-resource-manager/bicep/create-resource-group.md

@@ -3,7 +3,7 @@ title: Use Bicep to create a new resource group
 description: Describes how to use Bicep to create a new resource group in your Azure subscription.
 ms.topic: how-to
 ms.custom: devx-track-bicep
-ms.date: 09/26/2023
+ms.date: 09/26/2024
 ---
 
 # Create resource groups by using Bicep

articles/azure-resource-manager/bicep/deploy-cloud-shell.md

@@ -3,7 +3,7 @@ title: Deploy Bicep files with Cloud Shell
 description: Use Azure Resource Manager and Azure Cloud Shell to deploy resources to Azure. The resources are defined in a Bicep file.
 ms.topic: how-to
 ms.custom: devx-track-bicep, devx-track-arm-template
-ms.date: 06/23/2023
+ms.date: 09/26/2024
 ---
 
 # Deploy Bicep files from Azure Cloud Shell