Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into swa/supported-metrics

Author: craigshoemaker

.openpublishing.redirection.json

@@ -1,5 +1,84 @@
 {
   "redirections": [
+    {
+      "source_path": "articles/operator-5g-core/concept-centralized-lifecycle-management.md",
+      "redirect_url": "/previous-versions/azure/operator-5g-core/concept-centralized-lifecycle-management",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/operator-5g-core/concept-deployment-order.md",
+      "redirect_url": "/previous-versions/azure/operator-5g-core/concept-deployment-order",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/operator-5g-core/concept-observability-analytics.md",
+      "redirect_url": "/previous-versions/azure/operator-5g-core/concept-observability-analytics",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/operator-5g-core/concept-security.md",
+      "redirect_url": "/previous-versions/azure/operator-5g-core/concept-security",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/operator-5g-core/how-to-configure-network-function.md",
+      "redirect_url": "/previous-versions/azure/operator-5g-core/how-to-configure-network-function",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/operator-5g-core/how-to-delete-network-function-cluster.md",
+      "redirect_url": "/previous-versions/azure/operator-5g-core/how-to-delete-network-function-cluster",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/operator-5g-core/how-to-deploy-network-functions.md",
+      "redirect_url": "/previous-versions/azure/operator-5g-core/how-to-deploy-network-functions",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/operator-5g-core/how-to-deploy-observability.md",
+      "redirect_url": "/previous-versions/azure/operator-5g-core/how-to-deploy-observability",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/operator-5g-core/overview-product.md",
+      "redirect_url": "/previous-versions/azure/operator-5g-core/overview-product",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/operator-5g-core/quickstart-complete-prerequisites-deploy-azure-kubernetes-service.md",
+      "redirect_url": "/previous-versions/azure/operator-5g-core/quickstart-complete-prerequisites-deploy-azure-kubernetes-service",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/operator-5g-core/quickstart-complete-prerequisites-deploy-nexus-azure-kubernetes-service.md",
+      "redirect_url": "/previous-versions/azure/operator-5g-core/quickstart-complete-prerequisites-deploy-nexus-azure-kubernetes-service",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/operator-5g-core/quickstart-configure-extension-for-status-monitoring.md",
+      "redirect_url": "/previous-versions/azure/operator-5g-core/quickstart-configure-extension-for-status-monitoring",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/operator-5g-core/quickstart-deploy-5g-core.md",
+      "redirect_url": "/previous-versions/azure/operator-5g-core/quickstart-deploy-5g-core",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/operator-5g-core/quickstart-monitor-deployment-status.md",
+      "redirect_url": "/previous-versions/azure/operator-5g-core/quickstart-monitor-deployment-status",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/operator-5g-core/quickstart-subscription.md",
+      "redirect_url": "/previous-versions/azure/operator-5g-core/quickstart-subscription",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/operator-5g-core/tutorial-configure-network-function.md",
+      "redirect_url": "/previous-versions/azure/operator-5g-core/tutorial-configure-network-function",
+    },
     {
       "source_path": "articles/operator-call-protection/deployment-overview.md",
       "redirect_url": "/previous-versions/azure/operator-call-protection/deployment-overview",

articles/api-center/frequently-asked-questions.yml

@@ -6,7 +6,7 @@ metadata:
   ms.author: danlep
   ms.service: azure-api-center
   ms.topic: faq 
-  ms.date: 04/15/2024
+  ms.date: 11/15/2024
 
 title: "Frequently asked questions - Azure API Center"
 summary: |
@@ -21,21 +21,23 @@ sections:
 
           API Management is a runtime API governance and observability solution that enables you to expose APIs securely at scale, monitor their health, and analyze their usage. [Learn more](../api-management/api-management-key-concepts.md)
  
-          API Center is a design-time API governance and centralized API discovery solution. It acts as a repository and governance tool for all APIs within an organization, regardless of where they are in their lifecycle or where they are deployed. Use an API center to collect and maintain your organization's API inventory with rich metadata, and assess and help enforce API design consistency and quality.
+          API Center is a design-time API governance and centralized API discovery solution. It acts as a repository and governance tool for all APIs within an organization, regardless of where they are in their lifecycle or where they're deployed. Use an API center to collect and maintain your organization's API inventory with rich metadata, and assess and help enforce API design consistency and quality.
 
           Read more in [The Rising Significance of APIs - Azure API Management & API Center](https://techcommunity.microsoft.com/t5/azure-integration-services-blog/the-rising-significance-of-apis-azure-api-management-amp-api/ba-p/4181292).
 
       - question: How do I use Azure API Center with my API management solution?
         answer: |
           Azure API Center is a stand-alone Azure service that's complementary to Azure API Management and API management services from other providers. API Center provides a unified API inventory for all APIs in the organization, including APIs that don't run in API gateways (such as those that are still in design) and those that are managed with different API management solutions.
 
-          For APIs that are managed using an API management solution, Azure API Center can store metadata such as the runtime environment and deployment details. 
+          For APIs that are managed using an API management solution, Azure API Center can store metadata such as the runtime environment and deployment details. You can also link Azure API Management services as API sources for you inventory.
 
       - question: Does Azure API Center provide a developer portal?
         answer: Yes, you have an option to build and self-host a developer portal where developers can discover APIs in your API center and view API details. A reference implementation is available in the [API Center portal starter](https://github.com/Azure/APICenter-Portal-Starter.git) repository. [Learn more](enable-api-center-portal.md).
+
+          In the Azure API Center extension for Visual Studio Code, you can also provide an [API catalog](enable-platform-api-catalog-vscode-extension.md) view for app developers in your organization to discover APIs in your API center. 
 
       - question: Does Azure API Center support availability zones?
-        answer: Yes. The Azure API Center service runs in a multitenant environment on availability zone-enabled components. No additional configuration is required to enable availability zones for the service. 
+        answer: Yes. The Azure API Center service runs in a multitenant environment on availability zone-enabled components. No further configuration is required to enable availability zones for the service. 
 
       - question: Does my API center's data stay within the region I choose?
         answer: Yes, all data is stored in the region you choose when you create an API center.
@@ -56,4 +58,6 @@ sections:
 additionalContent: |
     ## Related content
 
-    To learn more, see [Azure API Center overview](overview.md).
+    * [Azure API Center overview](overview.md)
+    * [Build APIs | Microsoft Developer](https://developer.microsoft.com/build-apis
+

articles/api-center/key-concepts.md

@@ -4,7 +4,7 @@ description: Key concepts of Azure API Center. API Center inventories an organiz
 author: dlepow
 ms.service: azure-api-center
 ms.topic: conceptual
-ms.date: 04/23/2024
+ms.date: 11/15/2024
 ms.author: danlep
 ---
 
@@ -24,7 +24,7 @@ A top-level logical entity in Azure API Center, an API represents any real-world
 
 An API in the inventory can be managed by any API management solution, such as Azure [API Management](../api-management/api-management-key-concepts.md), Apigee API Management, Kong Konnect, MuleSoft API Management, or another platform. An API represented in Azure API Center can also be unmanaged.
 
-The API inventory in Azure API Center is designed to be created and managed by API program managers or IT administrators. 
+The API inventory in Azure API Center is designed to be created and managed by API program managers or IT administrators. Azure API Center also includes features for API developers to register API definitions directly from their development environments, such as Visual Studio Code or CI/CD pipelines.
 
 ## API version
 
@@ -34,6 +34,8 @@ API versioning is the practice of managing changes to an API and ensuring that t
 
 Each API version should ideally be defined by at least one definition, such as an OpenAPI definition for a REST API. Azure API Center allows any API definition file formatted as text (YAML, JSON, Markdown, and so on). You can upload OpenAPI, gRPC, GraphQL, AsyncAPI, WSDL, and WADL definitions, among others.
 
+To help with API governance, Azure API Center provides linting capabilities to analyze API definitions for quality and compliance with organizational standards.
+
 ## Environment
 
 An environment represents a location where an API runtime could be deployed, for example, an Azure API Management service, an Apigee API Management service, or a compute service such as a Kubernetes cluster, a Web App, or an Azure Function. Each environment is aligned with a lifecycle stage such as development, testing, staging, or production. An environment may also include information about developer portal or management interfaces. 
@@ -58,4 +60,5 @@ Azure API Center's metadata schema is compatible with JSON and YAML schema speci
 
 * [What is Azure API Center?](overview.md)
 * [Metadata for API governance](metadata.md)
+* [API analysis and linting](enable-managed-api-analysis-linting.md)
 

articles/api-center/manage-apis-azure-cli.md

@@ -39,10 +39,6 @@ az apic api create  --resource-group myResourceGroup \
     --title "Petstore API" --type "rest"
 ```
 
-> [!NOTE]
-> After creating an API, you can update the API's properties by using the [az apic api update](/cli/azure/apic/api#az_apic_api_update) command.
-
-
 ### Create an API version
 
 Use the [az apic api version create](/cli/azure/apic/api/version#az_apic_api_version_create) command to create a version for your API. 
@@ -117,8 +113,26 @@ az apic api register --resource-group myResourceGroup \
 * By default, the command sets the API's **Lifecycle stage** to *design*.
 * It creates an API version named according to the `version` property in the API definition (or *1-0-0* by default), and an API definition named according to the specification format (for example, *openapi*).
 
+## Update API properties
+
 After registering an API, you can update the API's properties by using the [az apic api update](/cli/azure/apic/api#az_apic_api_update), [az apic api version update](/cli/azure/apic/api/version#az_apic_api_version_update), and [az apic api definition update](/cli/azure/apic/api/definition#az_apic_api_definition_update) commands.
 
+The following example updates the title of the *petstore-api* API to *Petstore API v2*.
+
+```azurecli-interactive
+az apic api update --resource-group myResourceGroup \
+    --service-name myAPICenter --api-id petstore-api \
+    --title "Petstore API v2"
+```
+
+The following example sets the API's Boolean *internal* custom property to *false*.
+
+```azurecli-interactive
+az apic api update --resource-group myResourceGroup \
+    --service-name myAPICenter --api-id petstore-api \
+    --set custom_properties.internal=false
+```
+
 ## Delete API resources
 
 Use the [az apic api delete](/cli/azure/apic/api#az_apic_api_delete) command to delete an API and all of its version and definition resources. For example:

articles/api-center/overview.md

@@ -5,7 +5,7 @@ author: dlepow
 
 ms.service: azure-api-center
 ms.topic: overview
-ms.date: 04/15/2024
+ms.date: 11/15/2024
 ms.author: danlep 
 ms.custom: references_regions
 ---
@@ -17,7 +17,8 @@ Azure API Center enables tracking all of your APIs in a centralized location for
 With an API center, stakeholders throughout your organization - including API program managers, IT administrators, application developers, and API developers - can discover, reuse, and govern APIs.  
 
 > [!NOTE]
-> Azure API Center is a solution for design-time API governance and centralized API discovery. Azure also offers the API Management service, 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.
+> 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.
+
 
 ## Benefits
 
@@ -29,15 +30,20 @@ With an API center, stakeholders throughout your organization - including API pr
 
 * **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:
 
-* **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, or developer tooling including the Azure API Center extension for Visual Studio Code and CI/CD pipelines. 
+* **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 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. Developers can take advantage of the extension's integration with GitHub Copilot and GitHub Copilot for Azure to create API definitions from code or natural language descriptions.  
 
 * **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 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 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 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 discovery and reuse** - Enable enterprise developers and API program managers to discover APIs via an API Center portal or an [API platform catalog](enable-platform-api-catalog-vscode-extension.md) that's accessed using the Azure API Center Visual Studio Code extension.
 
@@ -68,7 +74,7 @@ Contoso's API ecosystem includes the following:
 
 * **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. 
 
-* **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: APIM-DEV, APIM-TEST and APIM-PROD. 
+* **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. 
 

articles/api-management/api-management-features.md

@@ -26,7 +26,7 @@ Each API Management [pricing tier](api-management-key-concepts.md#api-management
 | -------------------------------------------------------------------------------------------- | ----------- | --------- | --------- | --------- | ----- | -------- | ------- | ------- | 
 | Microsoft Entra integration<sup>1</sup>                                                             | No          | Yes       | No    | Yes      | Yes      | Yes      | Yes     | Yes |
 | Virtual network injection support                                                               | No          | Yes       | No    | No       | No       | No       | Yes    | Yes |
-| Private endpoint support for inbound connections                                                               | No          | Yes       | Yes    | No       | Yes       | No       | Yes  | No   |
+| Private endpoint support for inbound connections                                                               | No          | Yes       | Yes    | No       | Yes       | Yes       | Yes  | No   |
 | Outbound virtual network integration support                                                             | No          | No       | No    | No       | No       | Yes       | No    | Yes |
 | Multi-region deployment                                                                      | No          | No        | No    | No       | No       | No       | Yes     | No |
 | Availability zones                                                                           | No          | No        | No    | No       | No       | No       | Yes     | No  |