Merge pull request #305025 from MicrosoftDocs/main

Auto Publish – main to live - 2025-09-03 22:00 UTC

Author: learn-build-service-prod[bot]

articles/active-directory-b2c/whats-new-docs.md

@@ -1,7 +1,7 @@
 ---
 title: "What's new in Azure Active Directory business-to-customer (B2C)"
 description: "New and updated documentation for the Azure Active Directory business-to-customer (B2C)."
-ms.date: 08/01/2025
+ms.date: 09/03/2025
 ms.service: azure-active-directory
 ms.subservice: b2c
 ms.topic: whats-new
@@ -18,6 +18,13 @@ manager: CelesteDG
 
 Welcome to what's new in Azure Active Directory B2C documentation. This article lists new and significantly updated docs from the past three months. To learn what's new with the B2C service, see [What's new in Microsoft Entra ID](../active-directory/fundamentals/whats-new.md), [Azure AD B2C developer release notes](custom-policy-developer-notes.md) and [What's new in Microsoft Entra External ID](/entra/external-id/whats-new-docs).
 
+## August 2025
+
+### Updated articles
+
+- [Azure Active Directory B2C service limits and restrictions](service-limits.md) - Added new object limits
+- [StringCollection claims transformations](stringcollection-transformations.md) - Updated claim type information
+
 ## July 2025
 
 ### Updated articles
@@ -31,14 +38,4 @@ Welcome to what's new in Azure Active Directory B2C documentation. This article
 - [Configure Cloudflare Web Application Firewall with Azure Active Directory B2C](partner-cloudflare.md) - Added a note about Azure Front Door-managed certificates
 - [Azure AD B2C: Frequently asked questions (FAQ)](faq.yml) - Updated the note in the Azure AD B2C end-of-sale section
 - [Page layout versions](page-layout.md) - Added updates related to CAPTCHA
-- [Securing phone-based multifactor authentication](phone-based-mfa.md) - Added information on preventing fraudulent sign-ups 
-
-## April 2025
-
-### Updated articles
-
-This month, we added an important note to our articles stating that starting May 1, 2025, new customers can't purchase Azure AD B2C.  
-
-- [Manage administrator accounts in Azure Active Directory B2C](tenant-management-manage-administrator.md) - Updated the User page information
-- [Track user behavior in Azure AD B2C by using Application Insights](analytics-with-application-insights.md) - Replaced instrumentation key with connection string
-
+- [Securing phone-based multifactor authentication](phone-based-mfa.md) - Added information on preventing fraudulent sign-ups

articles/azure-functions/extension-bundles.md

@@ -2,7 +2,7 @@
 title: Azure Functions Extension Bundles
 description: Learn how to use extension bundles to make the correct set of Azure Functions trigger and binding extensions available in your non-.NET function code.
 ms.topic: concept-article
-ms.date: 08/06/2025
+ms.date: 08/26/2025
 
 #Customer intent: I want to understand how to correctly install extension bundles so that the functionality implemented in the extensions is available to my functions in my preferred development language.
 ---
@@ -15,7 +15,9 @@ This article applies only to Azure Functions developers who use non-.NET languag
 
 ## Overview
 
-Extension bundles add a predefined set of compatible binding extensions to your function app. Extension bundles are versioned. Each version contains a specific set of binding extensions that are verified to work together. Select a bundle version based on the versions of the extensions that you need in your app.
+Extension bundles add a predefined set of compatible binding extensions to your function app. A bundle contains all of the binding extensions currently supported by Functions. Extension bundles are versioned. Each version contains a specific set of binding extension versions that are verified to work together. 
+
+You should always use the latest bundle version in your app, when possible.
 
 When you create an Azure Functions project from a non-.NET template, extension bundles are already enabled in the app's `host.json` file.
 
@@ -25,20 +27,20 @@ You define an extension bundle reference in the `host.json` project file by addi
 
 [!INCLUDE [functions-extension-bundles-json](../../includes/functions-extension-bundles-json.md)]
 
-## Supported extension bundles
+## Bundle versions
 
-This table lists all `Microsoft.Azure.Functions.ExtensionBundle` bundle versions and the current [support state](#support-policy):
+This table lists all `Microsoft.Azure.Functions.ExtensionBundle` versions and the current [support state](#extension-bundles-support-policy):
 
 | Bundle version | Version in host.json | Support state<sup>*</sup> | 
 | --- | --- | --- | 
-| [4.x](https://github.com/Azure/azure-functions-extension-bundles/blob/main/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) | `[4.0.0, 5.0.0)` | Active | 
+| [4.x](https://github.com/Azure/azure-functions-extension-bundles/blob/main/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) | `[4.0.0, 5.0.0)`<br>`[4.*, 5.0.0)` | Active | 
 | [3.x](https://github.com/Azure/azure-functions-extension-bundles/blob/main-v3/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) | `[3.3.0, 4.0.0)` | Deprecated | 
 | [2.x](https://github.com/Azure/azure-functions-extension-bundles/blob/main-v2/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) | `[2.*, 3.0.0)` | Deprecated | 
 | [1.x](https://github.com/Azure/azure-functions-extension-bundles/blob/v1.x/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) | `[1.*, 2.0.0)` | Deprecated |
 
-<sup>*</sup> Deprecated bundle versions can use deprecated binding extension versions. For optimal supportability and reliability, you should [upgrade to bundle version 4.x](#upgrade-extension-bundles). 
+<sup>*</sup> Deprecated bundle versions can include deprecated binding extension versions. For optimal supportability and reliability, you should [upgrade to bundle version 4.x](#upgrade-extension-bundles). 
 
-The default extension bundles are defined via version ranges. To see the `extensions.json` definition file that generates the current bundle version for a major extension, select the link in the table.
+By default, extension bundles are defined via version ranges, which guarantees that the latest minor bundle version is used. Select a version link in the table to review the `extensions.json` file that defines the latest bundle for that major version.
 
 ## Considerations for extension bundles
 
@@ -52,7 +54,7 @@ Keep these considerations in mind when you work with extension bundles:
 
 It's important to keep your bundle version up-to-date so that your apps can continue to be eligible for new features, security patches, and performance optimizations. 
 
-To upgrade your app to the most recent bundle, edit the host.json file in the root of your app project. Set the value of `extensionBundle.version` to `[4.x,5.0.0)`, which should look like this in your host.json file:
+To upgrade your app to the most recent bundle, edit the host.json file in the root of your app project. Set the value of `extensionBundle.version` to `[4.0.0,5.0.0)`, which should look like this in your host.json file:
 
 ```json
 {
@@ -67,15 +69,32 @@ To upgrade your app to the most recent bundle, edit the host.json file in the ro
 Keep these considerations in mind when upgrading the extension bundle version used by your app:
 
 + The contents of the latest 4.x bundle can always be found at [this release page in the repo](https://github.com/Azure/azure-functions-extension-bundles/releases/latest).
-+ Review the reference documentation for any extensions used by your app to look for any breaking changes between versions. <!---For the list of extension versions included in the default bundle, see the `extension.json` project file linked [from this table](#supported-extension-bundles).--> You can review the [bundle releases page](https://github.com/Azure/azure-functions-extension-bundles/releases) in the bundles repo for specific bundle version tags.
++ Review the reference documentation for any extensions used by your app to look for any breaking changes between versions. For the list of extension versions included in the default bundle, see the `extension.json` project file linked [from this table](#bundle-versions). You can review the [bundle releases page](https://github.com/Azure/azure-functions-extension-bundles/releases) in the bundles repo for specific bundle version tags.
 + Always verify your app locally after upgrading the bundle version to ensure compatibility with the updated extensions. You can use the [func start](functions-core-tools-reference.md#func-start) command in Azure Functions Core Tools or F5 in Visual Studio or Visual Studio Code to run your function app locally.
 + The way that you trigger extensions to be updated based on changes to the bundle version in the host.json file depends on your app environment:
   + Local project: extensions are updated locally when Core Tools starts, either from the `func start` command or when debugging in your development tools.
   + Function app: extensions are updated when you deploy the updated host.json file to your function app in Azure.
 
-## Preview extension bundles
+## Extension bundles support policy
+
+Major version releases of an extension bundle can occur when there are breaking change updates in one of the contained binding extensions. These extension breaking changes require updates to the bundle to remain compatible with the underlying Azure SDKs. Upgrading the bundle ensures your apps continue to receive new features, performance improvements, and full product support.
+
+> [!NOTE]  
+> Because extension bundle updates are driven by updates in the underlying Azure SDKs, the support cycle for extension bundles generally follows the [support policies of the underlying Azure SDKs](https://azure.github.io/azure-sdk/policies_support.html).  
+>  
+> Microsoft notifies you when an extension bundle or a binding extension version is deprecated. These notifications might appear in different parts of your Functions experience, such as in host logs, Application Insights tables, or the Azure portal. When you encounter these notifications, you must start the process of planning for and upgrading your function apps to the latest supported extension bundle version. 
+
+The support cycle of extension bundles follows these distinct phases: 
+
+| Phase | Description |
+| ----- | ----- |  
+| **Preview** |Prerelease versions of specific binding extensions are maintained in a preview extension bundle (`Microsoft.Azure.Functions.ExtensionBundle.Preview`). You can use this preview extension bundle to take advantage of preview extensions and new behaviors in existing extensions before they reach general availability (GA). For more information, see [Work with preview extension bundles](#work-with-preview-extension-bundles). | 
+| **Active** | The most recent major version of extension bundles is considered to be the active version. We recommend this version for your function apps. |
+| **Deprecation** | The bundle version is superseded by a more recent release and is now deprecated. After a bundle is deprecated, it only receives critical bug fixes and security updates for a limited overlap period. This overlap is typically at least 12 months, which gives you time to plan, test, and upgrade your apps to the latest bundle version.<br/><br/>Function apps that continue to use a deprecated bundle can still run on the platform. However, to ensure access to new features, performance improvements, security patches, and full support, you must upgrade your function apps to a supported bundle version. |
+
+You can view the extension bundle versions and their included extensions in the [Azure Functions extension bundles repository](https://github.com/Azure/azure-functions-extension-bundles/releases). You can also view the Azure SDK releases page for an inventory of all Functions extensions. You can find individual .NET packages on [NuGet.org](https://nuget.org/). 
 
-Prerelease versions of specific binding extensions are maintained in a preview extension bundle: `Microsoft.Azure.Functions.ExtensionBundle.Preview`. You can use this preview extension bundle to take advantage of preview extensions and new behaviors in existing extensions before they reach general availability (GA).
+## Work with preview extension bundles
 
 Keep these considerations in mind when you choose to use a non-GA extension bundle:
 
@@ -94,21 +113,6 @@ Keep these considerations in mind when you choose to use a non-GA extension bund
   - Review the NuGet package versions of specific preview extensions that you're using.
   - Track significant updates or changes in the change logs published on NuGet.org for each preview extension.
 
-## Support policy
-
-Major version releases of extension bundles can occur when there are breaking changes or updates in the dependencies of the underlying binding extensions. These breaking changes, often introduced in Azure SDKs, require updates to the bundle to remain compatible.
-
-The support cycle of a GA extension bundle follows these distinct phases:
-
-| Phase | Description |
-| ----- | ----- |  
-| Active | The most recent major version of extension bundles is considered the active version. We recommend this version for your function apps. |
-| Notification| Microsoft provides advanced notice before retiring an extension bundle or a binding extension version. When you receive such a notification, you should begin planning to upgrade your function apps to the latest version of a supported extension bundle. This upgrade helps ensure that your apps continue to access new features, performance improvements, and support. |
-| Deprecation | When a new bundle version for a major extension becomes generally available, the previous version enters a 12-month deprecation phase. This overlap period gives you time to plan, test, and upgrade your apps before the previous version is retired. |
-| Retirement | After the retirement of an extension bundle, function apps that reference that specific version aren't eligible for new features, security patches, and performance optimizations. Function apps that use retired versions can still be created and deployed and are permitted to run on the platform. However, you must upgrade your function app to a supported bundle version before you can receive support.|
-
-You can view the extension bundle versions and their included extensions in the [GitHub repo for Azure Functions extension bundles](https://github.com/Azure/azure-functions-extension-bundles/releases). You can find individual .NET packages on [NuGet.org](https://nuget.org).
-
 ## Related content
 
 - To learn more about binding extensions, see [Register Azure Functions binding extensions](functions-bindings-register.md).

articles/azure-functions/functions-bindings-azure-sql.md

@@ -79,7 +79,7 @@ dotnet add package Microsoft.Azure.WebJobs.Extensions.Sql --prerelease
 ::: zone pivot="programming-language-javascript, programming-language-powershell,programming-language-python,programming-language-java"
 [!INCLUDE [functions-install-extension-bundle](../../includes/functions-install-extension-bundle.md)]
 
-If your app needs to use preview functionality, you should instead reference the latest version of the preview bundle. For more information, see [Preview extension bundles](extension-bundles.md#preview-extension-bundles).
+If your app needs to use preview functionality, you should instead reference the latest version of the preview bundle. For more information, see [Work with preview extension bundles](extension-bundles.md#work-with-preview-extension-bundles).
 
 You can view preview functionality on the [Azure Functions SQL Extensions release page](https://github.com/Azure/azure-functions-sql-extension/releases).
 

articles/azure-functions/functions-bindings-mcp.md

@@ -40,11 +40,13 @@ The Azure Functions MCP extension allows you to use Azure Functions to create re
 
 Add the extension to your project by installing this [NuGet package](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.Mcp) in your preferred way:
 
-`Microsoft.Azure.Functions.Worker.Extensions.Mcp`
+`Microsoft.Azure.Functions.Worker.Extensions.Mcp`  
 ::: zone-end  
-
 ::: zone pivot="programming-language-javascript,programming-language-typescript,programming-language-python,programming-language-java"  
+<!---At GA, replace with:
 [!INCLUDE [functions-install-extension-bundle](../../includes/functions-install-extension-bundle.md)]
+-->
+[!INCLUDE [functions-extension-bundles-json-preview](../../includes/functions-extension-bundles-json-preview.md)]  
 ::: zone-end
 
 ## host.json settings

articles/azure-functions/functions-bindings-openai.md

@@ -74,9 +74,10 @@ When using a vector database for storing content, you should also install at lea
 
 ::: zone-end
 ::: zone pivot="programming-language-java,programming-language-javascript,programming-language-typescript,programming-language-powershell,programming-language-python"
-
+<!---At GA, replace with:
 [!INCLUDE [functions-install-extension-bundle](../../includes/functions-install-extension-bundle.md)]
-
+-->
+[!INCLUDE [functions-extension-bundles-json-preview](../../includes/functions-extension-bundles-json-preview.md)]  
 ::: zone-end
 
 ## Connecting to OpenAI

articles/azure-functions/functions-bindings-rabbitmq.md

@@ -1,10 +1,8 @@
 ---
 title: Azure RabbitMQ bindings for Azure Functions
 description: Learn to send Azure RabbitMQ triggers and bindings in Azure Functions.
-author: ggailey777
 ms.topic: reference
-ms.date: 11/13/2024
-ms.author: glenga
+ms.date: 08/20/2025
 ms.custom: devx-track-extended-java, devx-track-js, devx-track-python
 zone_pivot_groups: programming-languages-set-functions-lang-workers
 ---
@@ -53,8 +51,7 @@ Add the extension to your project by installing this [NuGet package](https://www
 ::: zone pivot="programming-language-javascript,programming-language-python,programming-language-java,programming-language-powershell"  
 [!INCLUDE [functions-install-extension-bundle](../../includes/functions-install-extension-bundle.md)]
 ::: zone-end
-
-### host.json settings
+## host.json settings
 
 [!INCLUDE [functions-host-json-section-intro](../../includes/functions-host-json-section-intro.md)]
 
@@ -74,14 +71,12 @@ Add the extension to your project by installing this [NuGet package](https://www
 
 |Property  |Default | Description |
 |---------|---------|---------|
-|prefetchCount|30|Gets or sets the number of messages that the message receiver can simultaneously request and is cached.|
-|queueName|n/a| Name of the queue to receive messages from.|
-|connectionString|n/a|The RabbitMQ message queue connection string. <!---verify this--> The connection string is directly specified here and not through an app setting.|
-|port|0|(ignored if using connectionString) Gets or sets the Port used. Defaults to 0, which points to rabbitmq client's default port setting: 5672.|
+|`prefetchCount`|30|Gets or sets the number of messages that the message receiver can simultaneously request and is cached.|
+|`queueName`|n/a| Name of the queue to receive messages from.|
+|`connectionString`|n/a|The app setting that contains the RabbitMQ message queue connection string. |
+|`port`|0|(ignored if using connectionString) Gets or sets the Port used. Defaults to 0, which points to rabbitmq client's default port setting: 5672.|
 
 ## Related articles
 
 - [Run a function when a RabbitMQ message is created (Trigger)](./functions-bindings-rabbitmq-trigger.md)
 - [Send RabbitMQ messages from Azure Functions (Output binding)](./functions-bindings-rabbitmq-output.md)
-
-[extension bundle]: ./extension-bundles.md