Merge pull request #7385 from mrbullwinkle/mrb_09_30_2025_freshness_004

[Azure OpenAI] [Freshness 004]

Author: prmerger-automator[bot]

articles/ai-foundry/openai/concepts/customizing-llms.md

@@ -3,7 +3,7 @@ title: Azure OpenAI in Azure AI Foundry Models getting started with customizing
 titleSuffix: Azure OpenAI
 description: Learn more about the concepts behind customizing an LLM with Azure OpenAI.
 ms.topic: conceptual
-ms.date: 07/02/2025
+ms.date: 09/30/2025
 ms.service: azure-ai-openai
 manager: nitinme
 author: mrbullwinkle

articles/ai-foundry/openai/concepts/fine-tuning-considerations.md

@@ -4,7 +4,7 @@ description: Learn more about what you should take into consideration before fin
 manager: nitinme
 ms.service: azure-ai-openai
 ms.topic: conceptual 
-ms.date: 07/02/2025
+ms.date: 09/30/2025
 author: mrbullwinkle
 ms.author: mbullwin
 recommendations: false

articles/ai-foundry/openai/how-to/business-continuity-disaster-recovery.md

@@ -5,7 +5,7 @@ description: Considerations for implementing Business Continuity and Disaster Re
 manager: nitinme
 ms.service: azure-ai-openai
 ms.topic: how-to
-ms.date: 07/02/2025
+ms.date: 09/30/2025
 author: mrbullwinkle    
 ms.author: mbullwin
 recommendations: false

articles/ai-foundry/openai/how-to/dotnet-migration.md

@@ -7,15 +7,14 @@ ms.author: mbullwin
 ms.service: azure-ai-openai
 ms.custom: devx-track-dotnet
 ms.topic: how-to
-ms.date: 07/02/2025
+ms.date: 09/30/2025
 manager: nitinme
 ---
 
 # Migrate from 1.0 beta to 2.0 (`Azure.AI.OpenAI`)
 
 > [!NOTE]
-> This guide describes how to migrate an application that previously used a 1.0 beta version of the `Azure.AI.OpenAI` library to use the new 2.0 library.
-> For general guidance on using `OpenAI` and `Azure.AI.OpenAI` features, see [the OpenAI README](https://github.com/openai/openai-dotnet/blob/main/README.md) or [the Azure.AI.OpenAI README](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/openai/Azure.AI.OpenAI/README.md).
+> This guidance is no longer recommended. To take advantage of the latest v1 API refer to the [.NET programming language guide](../supported-languages.md).
 
 ## Setup
 

articles/ai-foundry/openai/how-to/migration.md

@@ -7,14 +7,17 @@ ms.author: mbullwin
 ms.service: azure-ai-openai
 ms.custom: devx-track-python
 ms.topic: how-to
-ms.date: 07/02/2025
+ms.date: 09/30/2025
 manager: nitinme
 ---
 
 # Migrating to the OpenAI Python API library 1.x
 
 OpenAI released a new version of the [OpenAI Python API library](https://github.com/openai/openai-python/). This guide is supplemental to [OpenAI's migration guide](https://github.com/openai/openai-python/discussions/742) and will help bring you up to speed on the changes specific to Azure OpenAI.
 
+> [!NOTE]
+> This guidance is no longer recommended. To take advantage of the latest v1 API refer to the [Python programming language guide](../supported-languages.md).
+
 ## Updates
 
 - This is a new version of the OpenAI Python API library.
@@ -35,7 +38,7 @@ OpenAI released a new version of the [OpenAI Python API library](https://github.
 ## Test before you migrate
 
 > [!IMPORTANT]
-> Automatic migration of your code using `openai migrate` is not supported with Azure OpenAI.
+> Automatic migration of your code using `openai migrate` isn't supported with Azure OpenAI.
 
 As this is a new version of the library with breaking changes, you should test your code extensively against the new release before migrating any production applications to rely on version 1.x. You should also review your code and internal processes to make sure that you're following best practices and pinning your production code to only versions that you have fully tested.
 
@@ -61,7 +64,7 @@ This provides context for what has changed and allows you to test the new librar
 
 # [OpenAI Python 1.x](#tab/python-new)
 
-You need to set the `model` variable to the deployment name you chose when you deployed the GPT-3.5-Turbo or GPT-4 models. Entering the model name results in an error unless you chose a deployment name that is identical to the underlying model name.
+You need to set the `model` variable to the deployment name you chose when you deployed the GPT-3.5-Turbo or GPT-4 models. Entering the model name results in an error unless you chose a deployment name that's identical to the underlying model name.
 
 ```python
 import os
@@ -90,7 +93,7 @@ Additional examples can be found in our [in-depth Chat Completion article](chatg
 
 # [OpenAI Python 0.28.1](#tab/python)
 
-You need to set the `engine` variable to the deployment name you chose when you deployed the GPT-3.5-Turbo or GPT-4 models. Entering the model name will result in an error unless you chose a deployment name that is identical to the underlying model name.
+You need to set the `engine` variable to the deployment name you chose when you deployed the GPT-3.5-Turbo or GPT-4 models. Entering the model name will result in an error unless you chose a deployment name that's identical to the underlying model name.
 
 ```python
 import os
@@ -536,7 +539,7 @@ asyncio.run(dall_e())
 ## Name changes
 
 > [!NOTE]
-> All a* methods have been removed; the async client must be used instead.
+> All `a*` methods have been removed; the async client must be used instead.
 
 | OpenAI Python 0.28.1 | OpenAI Python 1.x |
 | --------------- | --------------- |

articles/ai-foundry/openai/how-to/weights-and-biases-integration.md

@@ -7,7 +7,7 @@ ms.service: azure-ai-openai
 ms.custom:
   - ignite-2024
 ms.topic: how-to
-ms.date: 07/02/2025
+ms.date: 09/30/2025
 author: mrbullwinkle
 ms.author: mbullwin
 ---

articles/ai-foundry/openai/how-to/working-with-models.md

@@ -4,7 +4,7 @@ titleSuffix: Azure OpenAI
 description: Learn about managing model deployment life cycle, updates, & retirement.
 ms.service: azure-ai-openai
 ms.topic: conceptual
-ms.date: 07/02/2025
+ms.date: 09/30/2025
 ms.custom: references_regions, build-2023, build-2023-dataai, devx-track-azurepowershell
 manager: nitinme
 author: mrbullwinkle #ChrisHMSFT