Merge pull request #310175 from MicrosoftDocs/main

Auto Publish – main to live - 2026-01-06 18:00 UTC

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

articles/api-center/overview.md

@@ -5,54 +5,61 @@ author: dlepow
 
 ms.service: azure-api-center
 ms.topic: overview
-ms.date: 11/15/2024
+ms.date: 01/06/2025
 ms.author: danlep 
 ms.custom: references_regions
 ---
 
 # What is Azure API Center?
 
-Azure API Center enables tracking all of your APIs in a centralized location for discovery, reuse, and governance. Use an API center to develop and maintain a structured and organized inventory of your organization's APIs - regardless of their type, lifecycle stage, or deployment location - along with related information such as version details, API definition files, and common metadata. 
+Azure API Center enables you to track all of your APIs in a centralized location for discovery, reuse, and governance. Use an API center to develop and maintain a structured and organized inventory of your organization's APIs - regardless of their type, lifecycle stage, or deployment location - along with related information such as version details, API definition files, and common metadata. 
 
-With an API center, stakeholders throughout your organization - including API program managers, IT administrators, application developers, and API developers - can design, discover, reuse, and govern APIs.  
+> [!TIP]
+> Getting started with API Center just got easier! The Free plan is now available with no time constraints. [Limits](/azure/azure-resource-manager/management/azure-subscription-service-limits?toc=/azure/api-center/toc.json&bc=/azure/api-center/breadcrumb/toc.json#azure-api-center-limits) apply.
+
+By using an API center, stakeholders throughout your organization - including API program managers, IT administrators, application developers, and API developers - can design, discover, reuse, and govern APIs.  
 
 > [!NOTE]
 > Azure API Center is a solution for design-time API governance and centralized API discovery. Azure also offers complementary services such as Azure API Management, a solution for runtime API governance and observability using an API gateway. [Learn more](frequently-asked-questions.yml#what-s-the-difference-between-azure-api-management-and-azure-api-center) about the differences and how Azure API Center and API Management can work together.
 
-> [!TIP]
-> Getting started with API Center just got easier! The Free plan is now available with no time constraints. [Limits](/azure/azure-resource-manager/management/azure-subscription-service-limits?toc=/azure/api-center/toc.json&bc=/azure/api-center/breadcrumb/toc.json#azure-api-center-limits) apply.
-
 
 ## Benefits
 
-* **Create and maintain an organizational inventory​** - Organizations can build a **complete inventory of APIs** available in their organization. Register APIs managed in all of your API management solutions, including Azure API Management and platforms from other providers. Also include your unmanaged APIs and APIs under development. Foster communication and let API program managers and developers collaborate for increased API reuse, quality, security, compliance, and developer productivity.​
+* **Create and maintain an organizational inventory** - Build a **complete inventory of APIs** available in your organization. Register APIs managed in all of your API management solutions, including Azure API Management and platforms from other providers. Also include your unmanaged APIs and APIs under development. Foster communication and let API program managers and developers collaborate for increased API reuse, quality, security, compliance, and developer productivity.​
 
-*  **Govern your organization's APIs** - With more complete visibility into the APIs being developed and used within an organization, API program managers and IT administrators can govern this inventory to ensure it meets organizational standards by **defining custom metadata** and **analyzing API definitions** to enforce conformance to API style guidelines.​
+*  **Govern your organization's APIs** - With more complete visibility into the APIs being developed and used within your organization, API program managers and IT administrators can govern this inventory to ensure it meets organizational standards by **defining custom metadata** and **analyzing API definitions** to enforce conformance to API style guidelines.​
 
-* **Easy API discovery** - Organizations want to promote API reuse to maximize developer productivity and ensure developers are using the right APIs. Azure API Center helps program managers and developers discover the API inventory and filter using built-in and custom metadata. ​
+* **Easy API discovery** - Promote API reuse to maximize developer productivity and ensure developers are using the right APIs. Azure API Center helps program managers and developers discover the API inventory and filter using built-in and custom metadata. ​
 
 * **Accelerate API consumption** - Maximize developer productivity when consuming APIs and ensure they are consumed in a secure manner consistent with organizational standards. 
 
 
 ## Key capabilities
 
-Create and use an API center for the following:
+Create and use an API center for the following capabilities:
 
-* **API inventory management** - API developers and API program managers can register all of your organization's APIs for inclusion in a centralized inventory using the Azure portal, the Azure CLI, developer tooling such as CI/CD pipelines, and links to API sources such as Azure API Management services. 
+* **API inventory management** - API developers and API program managers can register all of your organization's APIs for inclusion in a centralized inventory by using the Azure portal, the Azure CLI, developer tooling such as CI/CD pipelines, and links to API sources such as Azure API Management services. 
 
-* **API design and development** - With the [Azure API Center extension for Visual Studio Code](build-register-apis-vscode-extension.md), developers can register APIs directly from the same development environment where they create their APIs and apps. 
+* **API design and development** - By using the [Azure API Center extension for Visual Studio Code](build-register-apis-vscode-extension.md), developers can register APIs directly from the same development environment where they create their APIs and apps. 
 
     Developers can take advantage of the extension's integration with GitHub Copilot to [create API definitions from code](build-register-apis-vscode-extension.md#generate-openapi-spec-from-api-code) and with GitHub Copilot for Azure to [design APIs with AI assistance](design-api-github-copilot-azure.md).  
 
 * **Real-world API representation** - Add real-world information about each API including versions and definitions such as OpenAPI definitions. List API deployments and associate them with runtime environments, for example, representing Azure API Management or other API management solutions.
 
-* **API governance** - Organize and filter APIs and related resources using built-in and custom metadata, to help with API governance and discovery by API consumers. Set up [linting and analysis](enable-managed-api-analysis-linting.md) to enforce API definition quality. 
+* **API governance** - Organize and filter APIs and related resources by using built-in and custom metadata, to help with API governance and discovery by API consumers. Set up [linting and analysis](enable-managed-api-analysis-linting.md) to enforce API definition quality. 
 
-    API developers can shift-left API design conformance checks into Visual Studio Code with integrated linting support and breaking change detection. Integrate with tools such as Dev Proxy to ensure that apps don't use unregistered [shadow APIs](discover-shadow-apis-dev-proxy.md) or APIs that don't meet organizational standards.
+    API developers can shift-left API design conformance checks into Visual Studio Code by using integrated linting support and breaking change detection. Integrate with tools such as Dev Proxy to ensure that apps don't use unregistered [shadow APIs](discover-shadow-apis-dev-proxy.md) or APIs that don't meet organizational standards.
 
-* **API discovery and reuse** - Enable enterprise developers and API program managers to discover APIs via an [API Center portal](set-up-api-center-portal.md). You can also enable the portal using the [Azure API Center Visual Studio Code extension](enable-api-center-portal-vs-code-extension.md).
+* **API discovery and reuse** - Enable enterprise developers and API program managers to discover APIs via an [API Center portal](set-up-api-center-portal.md). You can also enable the portal by using the [Azure API Center Visual Studio Code extension](enable-api-center-portal-vs-code-extension.md).
 
-For more about the entities you can manage and the capabilities in Azure API Center, see [Key concepts](key-concepts.md).
+For more information about the entities you can manage and the capabilities in Azure API Center, see [Key concepts](key-concepts.md).
+
+## Tiers and SKUs
+
+API Center is also offered in a Free plan and a Standard plan. [Learn more](../azure-resource-manager/management/azure-subscription-service-limits.md?toc=/azure/api-center/toc.json&bc=/azure/api-center/breadcrumb/toc.json#azure-api-center-limits).
+
+> [!NOTE]
+> Azure API Center is now included free with Azure API Management Premium and Standard tiers.
 
 ## Available regions
 Azure API Center is currently available in the following Azure regions:
@@ -64,27 +71,25 @@ Azure API Center is currently available in the following Azure regions:
 * France Central
 * Sweden Central
 * UK South
-* West Europe 
-
-API Center is offered in a Free plan and a Standard plan. [Learn more](../azure-resource-manager/management/azure-subscription-service-limits.md?toc=/azure/api-center/toc.json&bc=/azure/api-center/breadcrumb/toc.json#azure-api-center-limits).
+* West Europe
 
 ## Azure API Center and the API ecosystem
 
-Azure API Center can serve a key role in an organization's API ecosystem. Consider the hypothetical Contoso organization, which has adopted an API-first strategy, emphasizing the importance of APIs in their software development and integration. 
+Azure API Center can serve a key role in an organization's API ecosystem. Consider the hypothetical Contoso organization, which adopts an API-first strategy, emphasizing the importance of APIs in their software development and integration. 
 
 Contoso's API developers, app developers, API program managers, and API managers collaborate through Azure API Center to develop and use the organization's API inventory. See the following diagram and explanation.
 
 :::image type="content" source="media/overview/api-ecosystem-example.png" alt-text="Diagram showing API Center in an example API ecosystem.":::
 
-Contoso's API ecosystem includes the following:
+Contoso's API ecosystem includes the following features:
 
 * **API development** - Contoso's developers regularly build ASP.NET web APIs. They also create Azure Functions with HTTP triggers.
 
-* **API deployment environments** - Contoso deploys a portion of their APIs to Azure App Service. Another subset of their APIs is deployed to an Azure Function app. 
+* **API deployment environments** - Contoso deploys a portion of their APIs to Azure App Service. They deploy another subset of their APIs to an Azure Function app. 
 
-* **Azure API Management** - Contoso uses the Azure [API Management](../api-management/api-management-key-concepts.md) service to manage, publish, and secure their APIs. They use separate instances for Development, Test, and Production, each with a distinct name. 
+* **Azure API Management** - Contoso uses the Azure [API Management](../api-management/api-management-key-concepts.md) service to manage, publish, and secure their APIs. They use separate instances for development, test, and production, each with a distinct name. 
 
-* **Azure API Center** - Contoso has adopted Azure API Center as their centralized hub for API discovery, governance, and consumption. API Center serves as a structured and organized API hub that provides comprehensive information about all organizational APIs, maintaining related information including versions and associated deployments. 
+* **Azure API Center** - Contoso adopts Azure API Center as their centralized hub for API discovery, governance, and consumption. API Center serves as a structured and organized API hub that provides comprehensive information about all organizational APIs, maintaining related information including versions and associated deployments. 
 
 ## Next steps
 

articles/azure-app-configuration/how-to-connect-azure-front-door.md

@@ -88,7 +88,7 @@ Create a new Azure Front Door profile and connect it to your App Configuration s
 1. **Filter Configuration to scope the request**: Configure one or more filters to control which requests pass through Azure Front Door. This prevents accidental exposure of sensitive configuration and ensures only the settings your application needs are accessible. The filters here must exactly match those used in your application code; otherwise, requests will be rejected by Azure Front Door.
 
    > [!NOTE]
-   > To configure scoping filters correctly, ensure that the prefix filter in Azure Front Door exactly matches the selector your application uses to load keys from App Configuration. For example, if your application loads keys using the prefix "App1:", configure the same Starts with = "App1:" key filter in Azure Front Door. If your application instead uses a more specific key prefix such as "App1:Version", but Azure Front Door is allowlisted for "App1:" key filter (or vice versa), the request will be rejected because the selectors do not match exactly.
+   > To configure scoping filters correctly, ensure that the prefix filter in Azure Front Door exactly matches the selector your application uses to load keys from App Configuration. For example, if your application loads keys using the prefix "App1:", configure the same Starts with = "App1:" key filter in Azure Front Door. If your application instead uses a more specific key prefix such as "App1:Version", but Azure Front Door is allowlisted for "App1:" key filter (or vice versa), the request will be rejected because the selectors do not match exactly. See [examples for matching application filters with endpoint filters](https://github.com/Azure/AppConfiguration/blob/main/docs/AzureFrontDoor/readme.md).
 
    - **Key**: The key filter to apply when querying Azure App Configuration for key-values. Reserved characters: asterisk (`*`), comma (`,`), and backslash (`\`) must be escaped using a backslash (`\`) when filtering multiple key-values.
    - **Label**: The label filter to apply when querying Azure App Configuration for key-values. Reserved characters: asterisk (`*`), comma (`,`), and backslash (`\`) must be escaped using a backslash (`\`) when filtering multiple key-values.

articles/azure-app-configuration/how-to-load-azure-front-door-configuration-provider.md

@@ -76,7 +76,7 @@ For a complete sample app, refer to [JavaScript App with Azure App Configuration
 
 ## Considerations and edge cases
 
-- **Request scoping**: The key-value filters used by your application must match exactly the filters configured for the Azure Front Door endpoint; any mismatch will cause the request to be rejected. For example, if your endpoint is configured to allow access to keys starting with an "App1:" prefix, the application code must also load keys starting with "App1:". However, if your application loads keys starting with a more specific prefix like "App1:Prod:", the request is rejected.
+- **Request scoping**: The key-value filters used by your application must match exactly the filters configured for the Azure Front Door endpoint; any mismatch will cause the request to be rejected. For example, if your endpoint is configured to allow access to keys starting with an "App1:" prefix, the application code must also load keys starting with "App1:". However, if your application loads keys starting with a more specific prefix like "App1:Prod:", the request is rejected. See [examples for matching application filters with endpoint filters](https://github.com/Azure/AppConfiguration/blob/main/docs/AzureFrontDoor/readme.md).
 - **Exclusively loading feature flags**: If your application loads only feature flags, you should add two key filters in the Azure Front Door rules - one for ALL keys with no label and second for all keys starting with ".appconfig.featureflag/{YOUR-FEATURE-FLAG-PREFIX}".
 - **Refresh strategy**: Applications loading from Azure Front Door cannot use sentinel key refresh. If refresh is enabled, the application must be configured to [monitor all selected keys](./howto-best-practices.md#monitoring-all-selected-keys) for changes.
 - **Snapshot references**: If your application loads a key-value that is a [snapshot reference](./concept-snapshot-references.md), Azure Front Door must be configured to allowlist the referenced snapshot. Include the snapshot name in your Azure Front Door filters to enable snapshot resolution.

articles/azure-resource-manager/management/azure-services-resource-providers.md

@@ -121,7 +121,7 @@ The resource providers for database services are:
 | Microsoft.DBforMariaDB | [Azure Database for MariaDB](/azure/mariadb/) |
 | Microsoft.DBforMySQL | [Azure Database for MySQL](/azure/mysql/) |
 | Microsoft.DBforPostgreSQL | [Azure Database for PostgreSQL](/azure/postgresql/) |
-| Microsoft.DocumentDB | [Azure Cosmos DB](/azure/cosmos-db/) |
+| Microsoft.DocumentDB | [Azure Cosmos DB](/azure/cosmos-db/)<br /> [Azure DocumentDB](/azure/documentdb/) |
 | Microsoft.Sql | [Azure SQL Database](/azure/azure-sql/database/index)<br /> [Azure SQL Managed Instance](/azure/azure-sql/managed-instance/index) <br />[Azure Synapse Analytics](/azure/sql-data-warehouse/) |
 | Microsoft.SqlVirtualMachine | [SQL Server on Azure Virtual Machines](/azure/azure-sql/virtual-machines/windows/sql-server-on-azure-vm-iaas-what-is-overview) |
 | Microsoft.AzureData | [SQL Server enabled by Azure Arc](/sql/sql-server/azure-arc/overview) |

articles/azure-signalr/signalr-howto-diagnostic-logs.md

@@ -5,7 +5,7 @@ author: wanlwanl
 ms.service: azure-signalr-service
 ms.topic: how-to
 ms.date: 05/15/2023
-ms.author: wanl
+ms.author: jixin
 ---
 
 # Use resource logs to monitor SignalR Service

articles/azure-signalr/signalr-howto-troubleshoot-live-trace.md

@@ -2,7 +2,7 @@
 title: Use the live trace tool for Azure SignalR Service
 description: Learn how to use the live trace tool for Azure SignalR Service.
 author: wanlwanl
-ms.author: wanl
+ms.author: jixin
 ms.service: azure-signalr-service
 ms.topic: how-to 
 ms.date: 07/14/2022

articles/azure-web-pubsub/howto-azure-monitor.md

@@ -2,7 +2,7 @@
 title: Monitor Azure Web PubSub
 description: Learn how to monitor Azure Web PubSub with Azure Monitor
 author: wanlwanl
-ms.author: wanl
+ms.author: jixin
 ms.service: azure-web-pubsub
 ms.topic: how-to 
 ms.date: 05/15/2023

articles/azure-web-pubsub/howto-monitor-data-reference.md

@@ -5,7 +5,7 @@ author: wanlwanl
 ms.service: azure-web-pubsub
 ms.topic: how-to
 ms.date: 05/15/2023
-ms.author: wanl
+ms.author: jixin
 ---
 
 # Monitoring Azure Web PubSub data reference

articles/azure-web-pubsub/howto-troubleshoot-resource-logs.md

@@ -2,7 +2,7 @@
 title: Troubleshoot with Azure Web PubSub Service Resource Logs
 description: Learn what resource logs are and how to use them to troubleshoot common problems.
 author: wanlwanl
-ms.author: wanl
+ms.author: jixin
 ms.service: azure-web-pubsub
 ms.topic: how-to
 ms.date: 07/21/2022

articles/backup/azure-kubernetes-service-cluster-restore.md

@@ -6,7 +6,7 @@ ms.service: azure-backup
 ms.custom:
   - ignite-2023
   - ignite-2024
-ms.date: 01/30/2025
+ms.date: 01/06/2026
 author: AbhishekMallick-MS
 ms.author: v-mallicka
 # Customer intent: "As a cloud operations engineer, I want to restore a backed-up Azure Kubernetes Service cluster using Azure Backup, so that I can recover cluster resources and ensure continuity of services during disruptions."
@@ -126,7 +126,7 @@ Azure Backup for AKS currently supports the following two options when doing a r
 >[!Note]
 >AKS backup currently doesn't delete and recreate resources in the target cluster if they already exist. If you attempt to restore Persistent Volumes in the original location, delete the existing Persistent Volumes, and then do the restore operation.
 
-## Restore in secondary region
+## Restore the AKS clusters in secondary region
 
 To restore the AKS cluster in the secondary region, [configure Geo redundancy and Cross Region Restore in the Backup vault](azure-kubernetes-service-cluster-backup.md#create-a-backup-vault), and then [trigger restore](tutorial-restore-aks-backups-across-regions.md#restore-in-secondary-region).