Skip to content

Commit 823a3c1

Browse files
authored
Merge pull request #292180 from MicrosoftDocs/main
Publish to Live Thursday 4AM PST, 12/19
2 parents f2111fb + 3252bf3 commit 823a3c1

File tree

159 files changed

+775
-4922
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

159 files changed

+775
-4922
lines changed

.openpublishing.redirection.json

Lines changed: 79 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,84 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "articles/operator-5g-core/concept-centralized-lifecycle-management.md",
5+
"redirect_url": "/previous-versions/azure/operator-5g-core/concept-centralized-lifecycle-management",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path": "articles/operator-5g-core/concept-deployment-order.md",
10+
"redirect_url": "/previous-versions/azure/operator-5g-core/concept-deployment-order",
11+
"redirect_document_id": false
12+
},
13+
{
14+
"source_path": "articles/operator-5g-core/concept-observability-analytics.md",
15+
"redirect_url": "/previous-versions/azure/operator-5g-core/concept-observability-analytics",
16+
"redirect_document_id": false
17+
},
18+
{
19+
"source_path": "articles/operator-5g-core/concept-security.md",
20+
"redirect_url": "/previous-versions/azure/operator-5g-core/concept-security",
21+
"redirect_document_id": false
22+
},
23+
{
24+
"source_path": "articles/operator-5g-core/how-to-configure-network-function.md",
25+
"redirect_url": "/previous-versions/azure/operator-5g-core/how-to-configure-network-function",
26+
"redirect_document_id": false
27+
},
28+
{
29+
"source_path": "articles/operator-5g-core/how-to-delete-network-function-cluster.md",
30+
"redirect_url": "/previous-versions/azure/operator-5g-core/how-to-delete-network-function-cluster",
31+
"redirect_document_id": false
32+
},
33+
{
34+
"source_path": "articles/operator-5g-core/how-to-deploy-network-functions.md",
35+
"redirect_url": "/previous-versions/azure/operator-5g-core/how-to-deploy-network-functions",
36+
"redirect_document_id": false
37+
},
38+
{
39+
"source_path": "articles/operator-5g-core/how-to-deploy-observability.md",
40+
"redirect_url": "/previous-versions/azure/operator-5g-core/how-to-deploy-observability",
41+
"redirect_document_id": false
42+
},
43+
{
44+
"source_path": "articles/operator-5g-core/overview-product.md",
45+
"redirect_url": "/previous-versions/azure/operator-5g-core/overview-product",
46+
"redirect_document_id": false
47+
},
48+
{
49+
"source_path": "articles/operator-5g-core/quickstart-complete-prerequisites-deploy-azure-kubernetes-service.md",
50+
"redirect_url": "/previous-versions/azure/operator-5g-core/quickstart-complete-prerequisites-deploy-azure-kubernetes-service",
51+
"redirect_document_id": false
52+
},
53+
{
54+
"source_path": "articles/operator-5g-core/quickstart-complete-prerequisites-deploy-nexus-azure-kubernetes-service.md",
55+
"redirect_url": "/previous-versions/azure/operator-5g-core/quickstart-complete-prerequisites-deploy-nexus-azure-kubernetes-service",
56+
"redirect_document_id": false
57+
},
58+
{
59+
"source_path": "articles/operator-5g-core/quickstart-configure-extension-for-status-monitoring.md",
60+
"redirect_url": "/previous-versions/azure/operator-5g-core/quickstart-configure-extension-for-status-monitoring",
61+
"redirect_document_id": false
62+
},
63+
{
64+
"source_path": "articles/operator-5g-core/quickstart-deploy-5g-core.md",
65+
"redirect_url": "/previous-versions/azure/operator-5g-core/quickstart-deploy-5g-core",
66+
"redirect_document_id": false
67+
},
68+
{
69+
"source_path": "articles/operator-5g-core/quickstart-monitor-deployment-status.md",
70+
"redirect_url": "/previous-versions/azure/operator-5g-core/quickstart-monitor-deployment-status",
71+
"redirect_document_id": false
72+
},
73+
{
74+
"source_path": "articles/operator-5g-core/quickstart-subscription.md",
75+
"redirect_url": "/previous-versions/azure/operator-5g-core/quickstart-subscription",
76+
"redirect_document_id": false
77+
},
78+
{
79+
"source_path": "articles/operator-5g-core/tutorial-configure-network-function.md",
80+
"redirect_url": "/previous-versions/azure/operator-5g-core/tutorial-configure-network-function",
81+
},
382
{
483
"source_path": "articles/operator-call-protection/deployment-overview.md",
584
"redirect_url": "/previous-versions/azure/operator-call-protection/deployment-overview",

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

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ metadata:
66
ms.author: danlep
77
ms.service: azure-api-center
88
ms.topic: faq
9-
ms.date: 04/15/2024
9+
ms.date: 11/15/2024
1010

1111
title: "Frequently asked questions - Azure API Center"
1212
summary: |
@@ -21,21 +21,23 @@ sections:
2121
2222
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)
2323
24-
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.
24+
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.
2525

2626
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).
2727

2828
- question: How do I use Azure API Center with my API management solution?
2929
answer: |
3030
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.
3131
32-
For APIs that are managed using an API management solution, Azure API Center can store metadata such as the runtime environment and deployment details.
32+
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.
3333
3434
- question: Does Azure API Center provide a developer portal?
3535
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).
36+
37+
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.
3638

3739
- question: Does Azure API Center support availability zones?
38-
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.
40+
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.
3941

4042
- question: Does my API center's data stay within the region I choose?
4143
answer: Yes, all data is stored in the region you choose when you create an API center.
@@ -56,4 +58,6 @@ sections:
5658
additionalContent: |
5759
## Related content
5860
59-
To learn more, see [Azure API Center overview](overview.md).
61+
* [Azure API Center overview](overview.md)
62+
* [Build APIs | Microsoft Developer](https://developer.microsoft.com/build-apis
63+

articles/api-center/key-concepts.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Key concepts of Azure API Center. API Center inventories an organiz
44
author: dlepow
55
ms.service: azure-api-center
66
ms.topic: conceptual
7-
ms.date: 04/23/2024
7+
ms.date: 11/15/2024
88
ms.author: danlep
99
---
1010

@@ -24,7 +24,7 @@ A top-level logical entity in Azure API Center, an API represents any real-world
2424

2525
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.
2626

27-
The API inventory in Azure API Center is designed to be created and managed by API program managers or IT administrators.
27+
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.
2828

2929
## API version
3030

@@ -34,6 +34,8 @@ API versioning is the practice of managing changes to an API and ensuring that t
3434

3535
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.
3636

37+
To help with API governance, Azure API Center provides linting capabilities to analyze API definitions for quality and compliance with organizational standards.
38+
3739
## Environment
3840

3941
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
5860

5961
* [What is Azure API Center?](overview.md)
6062
* [Metadata for API governance](metadata.md)
63+
* [API analysis and linting](enable-managed-api-analysis-linting.md)
6164

articles/api-center/overview.md

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: dlepow
55

66
ms.service: azure-api-center
77
ms.topic: overview
8-
ms.date: 04/15/2024
8+
ms.date: 11/15/2024
99
ms.author: danlep
1010
ms.custom: references_regions
1111
---
@@ -17,7 +17,8 @@ Azure API Center enables tracking all of your APIs in a centralized location for
1717
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.
1818

1919
> [!NOTE]
20-
> 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.
20+
> 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.
21+
2122

2223
## Benefits
2324

@@ -29,15 +30,20 @@ With an API center, stakeholders throughout your organization - including API pr
2930

3031
* **Accelerate API consumption** - Maximize developer productivity when consuming APIs and ensure they are consumed in a secure manner consistent with organizational standards.
3132

33+
3234
## Key capabilities
3335

3436
Create and use an API center for the following:
3537

36-
* **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.
38+
* **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.
39+
40+
* **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.
3741

3842
* **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.
3943

40-
* **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.
44+
* **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.
45+
46+
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.
4147

4248
* **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.
4349

@@ -68,7 +74,7 @@ Contoso's API ecosystem includes the following:
6874

6975
* **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.
7076

71-
* **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.
77+
* **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.
7278

7379
* **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.
7480

articles/api-management/how-to-event-grid.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.custom: devx-track-azurecli
1111

1212
# Send events from API Management to Event Grid
1313

14-
[!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
14+
[!INCLUDE [api-management-availability-premium-dev-standard-basic-consumption](../../includes/api-management-availability-premium-dev-standard-basic-consumption.md)]
1515

1616
API Management integrates with [Azure Event Grid](../event-grid/overview.md) so that you can send event notifications to other services and trigger downstream processes. Event Grid is a fully managed event routing service that uses a publish-subscribe model. Event Grid has built-in support for Azure services like [Azure Functions](../azure-functions/functions-overview.md) and [Azure Logic Apps](../logic-apps/logic-apps-overview.md), and can deliver event alerts to non-Azure services using webhooks.
1717

articles/api-management/v2-service-tiers-overview.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -80,6 +80,7 @@ The following API Management capabilities are currently unavailable in the v2 ti
8080
* Inbound connection using a private endpoint
8181
* Upgrade to v2 tiers from classic tiers
8282
* CA Certificates
83+
* Sending events to Event Grid
8384

8485
**Developer portal**
8586
* Reports

articles/azure-resource-manager/management/move-support-resources.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1296,7 +1296,6 @@ Moves between Resource groups and subscriptions are supported for APIs that use
12961296
> [!div class="mx-tableFixed"]
12971297
> | Resource type | Resource group | Subscription | Region move |
12981298
> | ------------- | ----------- | ---------- | ---------- |
1299-
> | objectunderstandingaccounts | No | No | No |
13001299
> | remoterenderingaccounts | **Yes** | **Yes** | No |
13011300
13021301
## Microsoft.MobileNetwork

articles/azure-resource-manager/management/tag-support.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2199,8 +2199,6 @@ To get the same data as a file of comma-separated values, download [tag-support.
21992199
> [!div class="mx-tableFixed"]
22002200
> | Resource type | Supports tags | Tag in cost report |
22012201
> | ------------- | ----------- | ----------- |
2202-
> | objectAnchorsAccounts | Yes | Yes |
2203-
> | objectUnderstandingAccounts | Yes | Yes |
22042202
> | remoteRenderingAccounts | Yes | Yes |
22052203
22062204
## Microsoft.MobileNetwork

articles/azure-resource-manager/templates/deployment-complete-mode-deletion.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2199,8 +2199,6 @@ The resources are listed by resource provider namespace. To match a resource pro
21992199
> [!div class="mx-tableFixed"]
22002200
> | Resource type | Complete mode deletion |
22012201
> | ------------- | ----------- |
2202-
> | objectAnchorsAccounts | Yes |
2203-
> | objectUnderstandingAccounts | Yes |
22042202
> | remoteRenderingAccounts | Yes |
22052203
22062204
## Microsoft.MobileNetwork

articles/backup/backup-create-recovery-services-vault.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Create and configure Recovery Services vaults
33
description: Learn how to create and configure Recovery Services vaults, and how to restore in a secondary region by using Cross Region Restore.
44
ms.topic: how-to
5-
ms.date: 08/14/2023
5+
ms.date: 12/19/2024
66
ms.custom: references_regions, engagement-fy23
77
author: AbhishekMallick-MS
88
ms.author: v-abhmallick
@@ -60,7 +60,7 @@ Before you begin, consider the following information:
6060
A vault created with GRS redundancy includes the option to configure the Cross Region Restore feature. Every GRS vault has a banner that links to the documentation.
6161

6262
>[!Note]
63-
>Cross-region restore is currently not supported for machines running on Ultra disks. [Learn more about Ultra disk backup supportability](backup-support-matrix-iaas.md#ultra-disk-backup).
63+
>Cross-region restore is also supported for machines running on Ultra disks. [Learn more about Ultra disk backup supportability](backup-support-matrix-iaas.md#ultra-disk-backup).
6464
6565
![Screenshot that shows the banner about backup configuration.](./media/backup-azure-arm-restore-vms/banner.png)
6666

0 commit comments

Comments
 (0)