Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into WI-214554b-freshness-updates-march-2024

Author: AlizaBernstein

.openpublishing.redirection.azure-datalake-storage-gen1.json

@@ -289,16 +289,6 @@
             "source_path": "articles/data-lake-store/security-controls-policy.md",
             "redirect_url": "/previous-versions/azure/data-lake-store/security-controls-policy",
             "redirect_document_id": false
-          },
-          {
-            "source_path": "articles/storage/blobs/data-lake-storage-migrate-gen1-to-gen2.md",
-            "redirect_url": "/previous-versions/azure/storage/blobs/data-lake-storage-migrate-gen1-to-gen2",
-            "redirect_document_id": false
-          },
-          {
-            "source_path": "articles/storage/blobs/data-lake-storage-migrate-gen1-to-gen2-azure-portal.md",
-            "redirect_url": "/previous-versions/azure/storage/blobs/data-lake-storage-migrate-gen1-to-gen2-azure-portal",
-            "redirect_document_id": false
           }
 
     ]

.openpublishing.redirection.json

@@ -6705,6 +6705,21 @@
             "redirect_url": "/azure/active-directory/conditional-access/concept-conditional-access-cloud-apps",
             "redirect_document_id": true
         },
+        {
+            "source_path_from_root": "/articles/role-based-access-control/deny-assignments-portal.md",
+            "redirect_url": "/azure/role-based-access-control/deny-assignments",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/role-based-access-control/deny-assignments-powershell.md",
+            "redirect_url": "/azure/role-based-access-control/deny-assignments",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/role-based-access-control/deny-assignments-rest.md",
+            "redirect_url": "/azure/role-based-access-control/deny-assignments",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/scheduler/scheduler-intro.md",
             "redirect_url": "/azure/scheduler/migrate-from-scheduler-to-logic-apps",
@@ -10940,6 +10955,11 @@
             "redirect_url": "/azure/azure-health-insights/overview",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/azure-functions/functions-monitor-log-analytics.md",
+            "redirect_url": "/azure/azure-functions/monitor-functions",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/cloud-services-php-create-web-role.md",
             "redirect_url": "/azure/cloud-services/cloud-services-php-create-web-role",

.openpublishing.redirection.operator-5g-core.json

@@ -0,0 +1,49 @@
+{
+    "redirections": [
+        {
+            "source_path_from_root": "/articles/operator-5g-core/quickstart-configure-network-function.md ",
+            "redirect_url": "/azure/operator-5g-core/how-to-configure-network-function",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/operator-5g-core/quickstart-delete-network-function-cluster.md",
+            "redirect_url": "/azure/operator-5g-core/how-to-delete-network-function-cluster",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/operator-5g-core/quickstart-deploy-observability.md",
+            "redirect_url": "/azure/operator-5g-core/how-to-deploy-observability",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/operator-5g-core/how-to-complete-prerequisites-deploy-azure-kubernetes-service.md",
+            "redirect_url": "/azure/operator-5g-core/quickstart-complete-prerequisites-deploy-azure-kubernetes-service",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/operator-5g-core/how-to-complete-prerequisites-deploy-nexus-azure-kubernetes-service.md",
+            "redirect_url": "/azure/operator-5g-core/quickstart-complete-prerequisites-deploy-nexus-azure-kubernetes-service",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/operator-5g-core/how-to-deploy-5g-core.md",
+            "redirect_url": "/azure/operator-5g-core/quickstart-deploy-5g-core",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/operator-5g-core/how-to-monitor-deployment-status.md",
+            "redirect_url": "/azure/operator-5g-core/quickstart-monitor-deployment-status",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/operator-5g-core/how-to-perform-checks-post-deployment.md",
+            "redirect_url": "/azure/operator-5g-core/quickstart-perform-checks-post-deployment",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/operator-5g-core/quickstart-deploy-network-functions.md",
+            "redirect_url": "/azure/operator-5g-core/how-to-deploy-network-functions",
+            "redirect_document_id": false
+        }
+   ]
+}

articles/ai-services/TOC.yml

@@ -31,8 +31,8 @@
     href: cognitive-services-custom-subdomains.md
 - name: How-to
   items:
-  - name: Plan and manage costs 
-    href: plan-manage-costs.md
+  - name: Plan and manage costs
+    href: ../ai-studio/how-to/costs-plan-manage.md?context=/azure/ai-services/context/context
   - name: Increase rate limit
     href: autoscale.md
   - name: Use commitment tier pricing 

articles/ai-services/breadcrumb/toc.yml

@@ -0,0 +1,7 @@
+- name: Azure
+  tocHref: /azure/
+  topicHref: /azure/index
+  items:
+  - name: Azure AI services
+    tocHref: /azure/ai-services/
+    topicHref: /azure/ai-services/index

articles/ai-services/computer-vision/how-to/identity-access-token.md

@@ -9,25 +9,25 @@ manager: nitinme
 ms.service: azure-ai-vision
 ms.subservice: azure-ai-face
 ms.topic: how-to
-ms.date: 05/11/2023
+ms.date: 03/07/2024
 ms.author: pafarley
 ---
 
 # Use limited access tokens for Face
 
-Independent software vendors (ISVs) can manage the Face API usage of their clients by issuing access tokens that grant access to Face features which are normally gated. This allows client companies to use the Face API without having to go through the formal approval process.
+Independent software vendors (ISVs) can manage the Face API usage of their clients by issuing access tokens that grant access to Face features which are normally gated. This allows their client companies to use the Face API without having to go through the formal approval process.
 
 This guide shows you how to generate the access tokens, if you're an approved ISV, and how to use the tokens if you're a client. 
 
-The LimitedAccessToken feature is a part of the existing [Azure AI services token service](https://westus.dev.cognitive.microsoft.com/docs/services/57346a70b4769d2694911369/operations/issueScopedToken).  We have added a new operation for the purpose of bypassing the Limited Access gate for approved scenarios. Only ISVs that pass the gating requirements will be given access to this feature.
+The limited access token feature is a part of the existing [Azure AI services token service](https://westus.dev.cognitive.microsoft.com/docs/services/57346a70b4769d2694911369/operations/issueScopedToken).  We have added a new operation for the purpose of bypassing the Limited Access gate for approved scenarios. Only ISVs that pass the gating requirements will be given access to this feature.
 
 ## Example use case
 
-A company sells software that uses the Azure AI Face service to operate door access security systems. Their clients, individual manufacturers of door devices, subscribe to the software and run it on their devices. These client companies want to make Face API calls from their devices to perform Limited Access operations like face identification. By relying on access tokens from the ISV, they can bypass the formal approval process for face identification. The ISV, which has already been approved, can grant the client just-in-time access tokens.
+An example company sells software that uses the Azure AI Face service to operate door access security systems. Their clients, individual manufacturers of door devices, subscribe to the software and run it on their devices. These client companies want to make Face API calls from their devices to perform Limited Access operations like face identification. By relying on access tokens from the ISV, they can bypass the formal approval process for face identification. The ISV, which has already been approved, can grant the client just-in-time access tokens.
 
 ## Expectation of responsibility
 
-The issuing ISV  is responsible for ensuring that the tokens are used only for the approved purpose.
+The token-issuing ISV is responsible for ensuring that the tokens are used only for the approved purpose.
 
 If the ISV learns that a client is using the LimitedAccessToken for non-approved purposes, the ISV should stop generating tokens for that customer. Microsoft can track the issuance and usage of LimitedAccessTokens, and we reserve the right to revoke an ISV's access to the **issueLimitedAccessToken** API if abuse is not addressed.
 
@@ -80,7 +80,7 @@ The API should return a `200` response with the token in the form of a JSON web
 
 ## Step 3: Client application uses the token
 
-The ISV's application can then pass the LimitedAccessToken as an HTTP request header for future Face API requests on behalf of the client. This works independently of other authentication mechanisms, so no personal information of the client's is ever leaked to the ISV. 
+The ISV's application can then pass the limited access token as an HTTP request header for future Face API requests on behalf of the client. This works independently of other authentication mechanisms, so no personal information of the client's is ever leaked to the ISV. 
 
 > [!CAUTION]
 > The client doesn't need to be aware of the token value, as it can be passed in the background. If the client were to use a web monitoring tool to intercept the traffic, they'd be able to view the LimitedAccessToken header. However, because the token expires after a short period of time, they are limited in what they can do with it. This risk is known and considered acceptable.

articles/ai-services/content-safety/concepts/response-codes.md

@@ -8,7 +8,7 @@ manager: nitinme
 ms.service: azure-ai-content-safety
 ms.custom: build-2023
 ms.topic: conceptual
-ms.date: 05/09/2023
+ms.date: 03/07/2024
 ms.author: pafarley
 ---
 
@@ -18,9 +18,9 @@ The content APIs may return the following error codes:
 
 | Error Code    | Possible reasons   | Suggestions           |
 | ---------- | ------- | -------------------- |
-| InvalidRequestBody  | One or more fields in the request body do not match the API definition. | 1. Check the API version you specified in the API call. <br/>2. Check the corresponding API definition for the API version you selected. |
-| InvalidResourceName | The resource name you specified in the URL does not meet the requirements, like the blocklist name, blocklist term ID, etc. | 1. Check the API version you specified in the API call.  <br/>2. Check whether the given name has invalid characters according to the API definition. |
-| ResourceNotFound    | The resource you specified in the URL may not exist, like the blocklist name. | 1. Check the API version you specified in the API call. <br/> 2. Double check the existence of the resource specified in the URL. |
-| InternalError       | Some unexpected situations on the server side have been triggered. | 1. You may want to retry a few times after a small period and see it the issue happens again.  <br/>             2. Contact Azure Support if this issue persists. |
-| ServerBusy          | The server side cannot process the request temporarily.      | 1. You may want to retry a few times after a small period and see it the issue happens again.  <br/>2.Contact Azure Support if this issue persists. |
-| TooManyRequests     | The current RPS has exceeded the quota for your current SKU. | 1. Check the pricing table to understand the RPS quota.   <br/>2.Contact Azure Support if you need more QPS. |
+| InvalidRequestBody  | One or more fields in the request body do not match the API definition. | Check the API version you specified in the API call. <br/>Check the corresponding API definition for the API version you selected. |
+| InvalidResourceName | The resource name you specified in the URL does not meet the requirements, like the blocklist name, blocklist term ID, etc. | Check the API version you specified in the API call.  <br/>Check whether the given name has invalid characters according to the API definition. |
+| ResourceNotFound    | The resource you specified in the URL may not exist, like the blocklist name. | Check the API version you specified in the API call. <br/>Double check the existence of the resource specified in the URL. |
+| InternalError       | Some unexpected situations on the server side have been triggered. | You may want to retry a few times after a small period and see it the issue happens again.  <br/>             Contact Azure Support if this issue persists. |
+| ServerBusy          | The server side cannot process the request temporarily.      | You may want to retry a few times after a small period and see it the issue happens again.  <br/>Contact Azure Support if this issue persists. |
+| TooManyRequests     | The current RPS has exceeded the quota for your current SKU. | Check the pricing table to understand the RPS quota.   <br/>Contact Azure Support if you need more QPS. |

articles/ai-services/content-safety/how-to/use-blocklist.md

@@ -23,7 +23,7 @@ The default AI classifiers are sufficient for most content moderation needs. How
 ## Prerequisites
 
 * An Azure subscription - [Create one for free](https://azure.microsoft.com/free/cognitive-services/) 
-* Once you have your Azure subscription, <a href="https://aka.ms/acs-create"  title="Create a Content Safety resource"  target="_blank">create a Content Safety resource </a> in the Azure portal to get your key and endpoint. Enter a unique name for your resource, select the subscription you entered on the application form, and select a resource group, supported region, and supported pricing tier. Then select **Create**.
+* Once you have your Azure subscription, <a href="https://aka.ms/acs-create"  title="Create a Content Safety resource"  target="_blank">create a Content Safety resource </a> in the Azure portal to get your key and endpoint. Enter a unique name for your resource, select your subscription, and select a resource group, supported region (East US or West Europe), and supported pricing tier. Then select **Create**.
   * The resource takes a few minutes to deploy. After it finishes, Select **go to resource**. In the left pane, under **Resource Management**, select **Subscription Key and Endpoint**. The endpoint and either of the keys are used to call APIs.
 * One of the following installed:
   * [cURL](https://curl.haxx.se/) for REST API calls.

articles/ai-services/content-safety/includes/quickstarts/csharp-quickstart-image.md

@@ -7,7 +7,7 @@ manager: nitinme
 ms.service: azure-ai-content-safety
 ms.custom:
 ms.topic: include
-ms.date: 07/04/2023
+ms.date: 03/07/2024
 ms.author: pafarley
 ---
 
@@ -18,7 +18,7 @@ ms.author: pafarley
 * An Azure subscription - [Create one for free](https://azure.microsoft.com/free/cognitive-services/) 
 * The [Visual Studio IDE](https://visualstudio.microsoft.com/vs/) with workload .NET desktop development enabled. Or if you don't plan on using Visual Studio IDE, you need the current version of [.NET Core](https://dotnet.microsoft.com/download/dotnet-core).
 * [.NET Runtime](https://dotnet.microsoft.com/download/dotnet/) installed.
-* Once you have your Azure subscription, <a href="https://aka.ms/acs-create"  title="Create a Content Safety resource"  target="_blank">create a Content Safety resource </a> in the Azure portal to get your key and endpoint. Enter a unique name for your resource, select the subscription you entered on the application form, select a resource group, supported region, and supported pricing tier. Then select **Create**.
+* Once you have your Azure subscription, <a href="https://aka.ms/acs-create"  title="Create a Content Safety resource"  target="_blank">create a Content Safety resource </a> in the Azure portal to get your key and endpoint. Enter a unique name for your resource, select your subscription, and select a resource group, supported region (East US or West Europe), and supported pricing tier. Then select **Create**.
   * The resource takes a few minutes to deploy. After it finishes, Select **go to resource**. In the left pane, under **Resource Management**, select **Subscription Key and Endpoint**. The endpoint and either of the keys are used to call APIs.
 
 ## Set up application

articles/ai-services/content-safety/includes/quickstarts/csharp-quickstart-text.md

@@ -17,7 +17,7 @@ ms.author: pafarley
 
 * An Azure subscription - [Create one for free](https://azure.microsoft.com/free/cognitive-services/) 
 * The [Visual Studio IDE](https://visualstudio.microsoft.com/vs/) with workload .NET desktop development enabled. Or if you don't plan on using Visual Studio IDE, you need the current version of [.NET Core](https://dotnet.microsoft.com/download/dotnet-core).
-* Once you have your Azure subscription, <a href="https://aka.ms/acs-create"  title="Create a Content Safety resource"  target="_blank">create a Content Safety resource </a> in the Azure portal to get your key and endpoint. Enter a unique name for your resource, select the subscription you entered on the application form, select a resource group, supported region, and supported pricing tier. Then select **Create**.
+* Once you have your Azure subscription, <a href="https://aka.ms/acs-create"  title="Create a Content Safety resource"  target="_blank">create a Content Safety resource </a> in the Azure portal to get your key and endpoint. Enter a unique name for your resource, select your subscription, and select a resource group, supported region (East US or West Europe), and supported pricing tier. Then select **Create**.
   * The resource takes a few minutes to deploy. After it finishes, Select **go to resource**. In the left pane, under **Resource Management**, select **Subscription Key and Endpoint**. The endpoint and either of the keys are used to call APIs.
 
 ## Set up application