Merge remote-tracking branch 'upstream/main' into december-synapse-freshness

Author: whhender

.openpublishing.redirection.json

@@ -1,5 +1,118 @@
 {
   "redirections": [
+    {
+      "source_path": "articles/cdn/akamai-retirement-faq.md",
+      "redirect_url": "/previous-versions/azure/cdn/akamai-retirement-faq",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/migrate/replicate-using-expressroute.md",
+      "redirect_url": "/azure/migrate/discover-and-assess-using-private-endpoints",
+      "redirect_document_id": false
+    },
+    {
+      "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",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/operator-call-protection/onboarding.md",
+      "redirect_url": "/previous-versions/azure/operator-call-protection/onboarding",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/operator-call-protection/overview.md",
+      "redirect_url": "/previous-versions/azure/operator-call-protection/overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/operator-call-protection/responsible-ai-faq.md",
+      "redirect_url": "/previous-versions/azure/operator-call-protection/responsible-ai-faq",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/operator-call-protection/set-up-operator-call-protection.md",
+      "redirect_url": "/previous-versions/azure/operator-call-protection/set-up-operator-call-protection",
+    },
     {
       "source_path": "articles/private-multi-access-edge-compute-mec/overview.md",
       "redirect_url": "/previous-versions/azure/private-multi-access-edge-compute-mec/overview",
@@ -4358,6 +4471,11 @@
       "source_path_from_root": "/articles/fasttrack/index.yml",
       "redirect_url": "/azure",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/sentinel/data-connectors/threat-intelligence-upload-indicators-api.md",
+      "redirect_url": "/azure/sentinel/data-connectors/threat-intelligence-upload-api",
+      "redirect_document_id": false
     }
   ]
 }

articles/active-directory-b2c/add-api-connector-token-enrichment.md

@@ -169,7 +169,7 @@ A claim provides temporary storage of data during an Azure AD B2C policy executi
 </ClaimType>
 ```
 ## Add the RESTful API technical profile 
-A [Restful technical profile](restful-technical-profile.md) provides support for interfacing with your own RESTful service. Azure AD B2C sends data to the RESTful service in an `InputClaims` collection and receives data back in an `OutputClaims` collection. Find the **ClaimsProviders** element in your <em>**`TrustFrameworkExtensions.xml`**</em> file and add a new claims provider as follows:
+A [RESTful technical profile](restful-technical-profile.md) provides support for interfacing with your own RESTful service. Azure AD B2C sends data to the RESTful service in an `InputClaims` collection and receives data back in an `OutputClaims` collection. Find the **ClaimsProviders** element in your <em>**`TrustFrameworkExtensions.xml`**</em> file and add a new claims provider as follows:
 ```xml
 <ClaimsProvider>
   <DisplayName>REST APIs</DisplayName>

articles/active-directory-b2c/add-api-connector.md

@@ -442,7 +442,7 @@ A claim provides temporary storage of data during an Azure AD B2C policy executi
 
 ## Add the RESTful API technical profile 
 
-A [Restful technical profile](restful-technical-profile.md) provides support for interfacing to your own RESTful service. Azure AD B2C sends data to the RESTful service in an `InputClaims` collection and receives data back in an `OutputClaims` collection. Find the **ClaimsProviders** element and add a new claims provider as follows:
+A [RESTful technical profile](restful-technical-profile.md) provides support for interfacing to your own RESTful service. Azure AD B2C sends data to the RESTful service in an `InputClaims` collection and receives data back in an `OutputClaims` collection. Find the **ClaimsProviders** element and add a new claims provider as follows:
 
 ```xml
 <ClaimsProvider>

articles/active-directory-b2c/custom-policy-reference-sso.md

@@ -52,7 +52,7 @@ The following table shows which session provider to use depending on the type of
 |Session provider  |Applicable technical profile types| Purpose |Write claims|Read claims|
 |---------|---------|---------|---------|---------|
 |[DefaultSSOSessionProvider](#defaultssosessionprovider)  | [Self-asserted](self-asserted-technical-profile.md), [Microsoft Entra ID](active-directory-technical-profile.md), [Microsoft Entra multifactor authentication](multi-factor-auth-technical-profile.md), [Claims transformation](claims-transformation-technical-profile.md)| Skips technical profile execution.| Yes | Yes |
-|[ExternalLoginSSOSessionProvider](#externalloginssosessionprovider) | [OAuth1 identity provider](oauth1-technical-profile.md), [Oauth2 identity provider](oauth2-technical-profile.md), [OpenID Connect identity provider](openid-connect-technical-profile.md), [SAML identity provider](saml-identity-provider-technical-profile.md)| Accelerate identity provider selection page. Performing single-logout.|Yes|Yes|
+|[ExternalLoginSSOSessionProvider](#externalloginssosessionprovider) | [OAuth1 identity provider](oauth1-technical-profile.md), [OAuth2 identity provider](oauth2-technical-profile.md), [OpenID Connect identity provider](openid-connect-technical-profile.md), [SAML identity provider](saml-identity-provider-technical-profile.md)| Accelerate identity provider selection page. Performing single-logout.|Yes|Yes|
 |[OAuthSSOSessionProvider](#oauthssosessionprovider) |[JWT token issuer](jwt-issuer-technical-profile.md) | Manages session between OAuth2 or OpenId Connect relying party and Azure AD B2C. Performs single-logout. | No | No |
 |[SamlSSOSessionProvider](#samlssosessionprovider) | [SAML token issuer](saml-issuer-technical-profile.md) | Manages session between SAML relying party and Azure AD B2C. Performs single-logout. | No | No |
 |[NoopSSOSessionProvider](#noopssosessionprovider) |Any| Suppress any technical profile from being part of the session.| No | No |
@@ -291,7 +291,7 @@ To use the `SM-Saml-issuer` session management technical profile, add a referenc
 The `NoopSSOSessionProvider` session provider is used to suppress single sign on behavior. Technical profiles that use this type of session provider will always be processed, even when the user has an active session. This type of session provider can be useful to force particular technical profiles to always run, for example:
 
 - [Claims transformation](claims-transformation-technical-profile.md) - To create, or transform claims that are later used to determine which orchestration steps to process or skip.
-- [Restful](restful-technical-profile.md) - Fetch updated data from a Restful service each time the policy runs. You can also call a Restful for extended logging, and auditing.
+- [RESTful](restful-technical-profile.md) - Fetch updated data from a RESTful service each time the policy runs. You can also call a RESTful for extended logging, and auditing.
 - [Self-asserted](self-asserted-technical-profile.md) - Force the user to provide data each time the policy runs. For example, verify emails with one-time pass-code, or ask the user's consent.
 - [Phonefactor](phone-factor-technical-profile.md) - Force the user to perform multifactor authentication as part of a "step up authentication" even during subsequent logons (single sign-on).
 

articles/active-directory-b2c/identity-provider-google.md

@@ -51,7 +51,7 @@ To enable sign-in for users with a Google account in Azure Active Directory B2C
     1. In the **Authorized domains** section, enter *b2clogin.com*.
     1. In the **Developer contact information** section, enter comma separated emails for Google to notify you about any changes to your project. 
     1. Select **Save**.
-1. Select **Credentials** in the left menu, and then select **Create credentials** > **Oauth client ID**.
+1. Select **Credentials** in the left menu, and then select **Create credentials** > **OAuth client ID**.
 1. Under **Application type**, select **Web application**.
     1. Enter a **Name** for your application.
     1. For the **Authorized JavaScript origins**, enter `https://your-tenant-name.b2clogin.com`. If you use a [custom domain](custom-domain.md), enter `https://your-domain-name`.

articles/active-directory-b2c/oauth2-error-technical-profile.md

@@ -102,7 +102,7 @@ Use these steps to generate custom values of error code and error message:
     </ClaimsTransformations> -->
     ```
 
-1. Add the two claims transformations in the `OutputClaimsTransformations` element of any technical profile before Oauth2 technical that you define:
+1. Add the two claims transformations in the `OutputClaimsTransformations` element of any technical profile before OAuth2 technical that you define:
 
     ```xml
         <OutputClaimsTransformations>
@@ -160,7 +160,7 @@ In the following example:
 </UserJourney>
 ```
 
-Optionally, you can use preconditions to manipulate the Oauth2 error technical profile. For example, if there is no email claim, you can set to call Oauth2 error technical profile:
+Optionally, you can use preconditions to manipulate the OAuth2 error technical profile. For example, if there is no email claim, you can set to call OAuth2 error technical profile:
 
 ```xml
 <OrchestrationStep Order="3" Type="SendClaims" CpimIssuerTechnicalProfileReferenceId="ReturnOAuth2Error">

articles/active-directory-b2c/secure-rest-api.md

@@ -243,7 +243,7 @@ Authorization: Bearer <token>
 
 A bearer token is an opaque string. It can be a JWT access token or any string that the REST API expects Azure AD B2C to send in the authorization header. Azure AD B2C supports the following types:
 
-- **Bearer token**. To be able to send the bearer token in the Restful technical profile, your policy needs to first acquire the bearer token and then use it in the RESTful technical profile.  
+- **Bearer token**. To be able to send the bearer token in the RESTful technical profile, your policy needs to first acquire the bearer token and then use it in the RESTful technical profile.  
 - **Static bearer token**. Use this approach when your REST API issues a long-term access token. To use a static bearer token, create a policy key and make a reference from the RESTful technical profile to your policy key. 
 
 ## Using OAuth2 Bearer  
@@ -587,5 +587,5 @@ The following XML snippet is an example of a RESTful technical profile configure
 ::: zone-end
 
 ::: zone pivot="b2c-custom-policy"
-- Learn more about the [Restful technical profile](restful-technical-profile.md) element in the custom policy reference.
+- Learn more about the [RESTful technical profile](restful-technical-profile.md) element in the custom policy reference.
 ::: zone-end

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
+