Merge branch 'main' of https://github.com/seesharprun/azure-docs-pr into cosmos-network-bandwidth

Author: seesharprun

.openpublishing.redirection.json

@@ -941,11 +941,6 @@
             "redirect_url": "/azure/site-recovery/hyper-v-azure-support-matrix",
             "redirect_document_id": false
         },
-        {
-            "source_path": "articles/site-recovery/unregister-vmm-server-script.md",
-            "redirect_url": "/azure/site-recovery/azure-to-azure-autoupdate",
-            "redirect_document_id": false
-        },
         {
             "source_path": "articles/site-recovery/hyper-v-vmm-secondary-support-matrix.md",
             "redirect_url": "/azure/site-recovery/azure-to-azure-autoupdate",
@@ -1001,6 +996,26 @@
             "redirect_url": "/azure/container-registry/container-registry-configure-conditional-access.md",
             "redirect_document_id": false 
         },
+        {
+            "source_path": "articles/container-registry/tutorial-artifact-streaming.md",
+            "redirect_url": "/azure/container-registry/container-registry-artifact-streaming",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/container-registry/tutorial-artifact-streaming-cli.md",
+            "redirect_url": "/azure/container-registry/container-registry-artifact-streaming",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/container-registry/tutorial-artifact-streaming-portal.md",
+            "redirect_url": "/azure/container-registry/container-registry-artifact-streaming",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/container-registry/tutorial-artifact-streaming-troubleshoot.md",
+            "redirect_url": "/azure/container-registry/troubleshoot-artifact-streaming",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/site-recovery/vmware-physical-secondary-disaster-recovery.md",
             "redirect_url": "/azure/site-recovery/vmware-physical-secondary-architecture",
@@ -22531,6 +22546,11 @@
             "source_path_from_root": "/articles/virtual-network/ip-services/virtual-networks-static-private-ip-classic-ps.md",
             "redirect_url": "/updates/azure-classic-resource-providers-will-be-retired-on-31-august-2024/",
             "redirect_document_id": false  
+        },
+        {
+            "source_path_from_root": "/articles/orbital/overview-analytics.md",
+            "redirect_url": "/azure/orbital/overview",
+            "redirect_document_id": false  
         }
     ]
 }

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

@@ -1,15 +1,10 @@
 ---
 title: Token enrichment  - Azure Active Directory B2C
 description: Enrich tokens with claims from external identity data sources using APIs or outbound webhooks.
-
 author: garrodonnell
 manager: CelesteDG
-
 ms.service: active-directory
-
-ms.custom: 
 ms.topic: how-to
-
 ms.date: 01/17/2023
 ms.author: godonnell
 ms.subservice: B2C

articles/active-directory-b2c/conditional-access-identity-protection-overview.md

@@ -1,19 +1,15 @@
 ---
 title: Identity Protection and Conditional Access in Azure AD B2C
 description: Learn how Identity Protection gives you visibility into risky sign-ins and risk detections. Find out how and Conditional Access lets you enforce organizational policies based on risk events in your Azure AD B2C tenants.
-
 ms.service: active-directory
 ms.subservice: conditional-access
 ms.topic: overview
 ms.date: 01/11/2024
-
 ms.author: kengaderdus
 author: kengaderdus
 manager: CelesteDG
-
 ms.collection: M365-identity-device-management
 
-
 #Customer intent: As an Azure AD B2C application owner, I want to enhance the security of my applications by using Identity Protection and Conditional Access, so that I can detect and respond to risky authentications and enforce organizational policies.
 
 ---

articles/active-directory-b2c/configure-a-sample-node-web-app.md

@@ -1,13 +1,13 @@
 ---
 title: Configure authentication in a sample Node.js web application by using Azure Active Directory B2C (Azure AD B2C)
-description: This article discusses how to use Azure Active Directory B2C to sign in and sign up users in a Node.js web application. 
+description: This article discusses how to use Azure Active Directory B2C to sign in and sign up users in a Node.js web application.
 titleSuffix: Azure AD B2C
 
 author: kengaderdus
 manager: CelesteDG
 ms.service: active-directory
 
-ms.custom: devx-track-js, devx-track-linux
+ms.custom: devx-track-js, linux-related-content
 ms.topic: how-to
 ms.date: 01/11/2024
 ms.author: kengaderdus
@@ -20,14 +20,14 @@ ms.subservice: B2C
 
 # Configure authentication in a sample Node.js web application by using Azure Active Directory B2C
 
-This sample article uses a sample Node.js application to show how to add Azure Active Directory B2C (Azure AD B2C) authentication to a Node.js web application. The sample application enables users to sign in, sign out, update profile and reset password using Azure AD B2C user flows. The sample web application uses [Microsoft Authentication Library (MSAL) for Node](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-node) to handle authentication and authorization. 
+This sample article uses a sample Node.js application to show how to add Azure Active Directory B2C (Azure AD B2C) authentication to a Node.js web application. The sample application enables users to sign in, sign out, update profile and reset password using Azure AD B2C user flows. The sample web application uses [Microsoft Authentication Library (MSAL) for Node](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-node) to handle authentication and authorization.
 
 In this article, you’ll do the following tasks:
 
 - Register a web application in the Azure portal.
 - Create combined **Sign in and sign up**, **Profile editing**, and **Password reset** user flows for the app in the Azure portal.
 - Update a sample Node application to use your own Azure AD B2C application and user flows.
-- Test the sample application. 
+- Test the sample application.
 
 ## Prerequisites
 
@@ -37,15 +37,15 @@ In this article, you’ll do the following tasks:
 
 ## Step 1: Configure your user flows
 
-[!INCLUDE [active-directory-b2c-app-integration-add-user-flow](../../includes/active-directory-b2c-app-integration-add-user-flow.md)] 
+[!INCLUDE [active-directory-b2c-app-integration-add-user-flow](../../includes/active-directory-b2c-app-integration-add-user-flow.md)]
 
 ## Step 2: Register a web application
 
-To enable your application sign in with Azure AD B2C, register your app in the Azure AD B2C directory. The app registration establishes a trust relationship between the app and Azure AD B2C.  
+To enable your application sign in with Azure AD B2C, register your app in the Azure AD B2C directory. The app registration establishes a trust relationship between the app and Azure AD B2C.
 
-During app registration, you'll specify the *Redirect URI*. The redirect URI is the endpoint to which the user is redirected by Azure AD B2C after they authenticate with Azure AD B2C. The app registration process generates an *Application ID*, also known as the *client ID*, that uniquely identifies your app. After your app is registered, Azure AD B2C uses both the application ID, and the redirect URI to create authentication requests. 
+During app registration, you'll specify the *Redirect URI*. The redirect URI is the endpoint to which the user is redirected by Azure AD B2C after they authenticate with Azure AD B2C. The app registration process generates an *Application ID*, also known as the *client ID*, that uniquely identifies your app. After your app is registered, Azure AD B2C uses both the application ID, and the redirect URI to create authentication requests.
 
-### Step 2.1: Register the app 
+### Step 2.1: Register the app
 
 To register the web app, follow these steps:
 
@@ -54,7 +54,7 @@ To register the web app, follow these steps:
 1. In the Azure portal, search for and select **Azure AD B2C**.
 1. Select **App registrations**, and then select **New registration**.
 1. Under **Name**, enter a name for the application (for example, *webapp1*).
-1. Under **Supported account types**, select **Accounts in any identity provider or organizational directory (for authenticating users with user flows)**. 
+1. Under **Supported account types**, select **Accounts in any identity provider or organizational directory (for authenticating users with user flows)**.
 1. Under **Redirect URI**, select **Web** and then, in the URL box, enter `http://localhost:3000/redirect`.
 1. Under **Permissions**, select the **Grant admin consent to openid and offline_access permissions** checkbox.
 1. Select **Register**.
@@ -106,7 +106,7 @@ The `views` folder contains Handlebars files for the application's user interfac
 
 ## Step 5: Configure the sample web app
 
-Open your web app in a code editor such as Visual Studio Code. Under the project root folder, open the *.env* file. This file contains information about your Azure AD B2C identity provider. Update the following app settings properties:  
+Open your web app in a code editor such as Visual Studio Code. Under the project root folder, open the *.env* file. This file contains information about your Azure AD B2C identity provider. Update the following app settings properties:
 
 |Key  |Value  |
 |---------|---------|
@@ -129,7 +129,7 @@ Your final configuration file should look like the following sample:
 You can now test the sample app. You need to start the Node server and access it through your browser on `http://localhost:3000`.
 
 1. In your terminal, run the following code to start the Node.js web server:
- 
+
    ```bash
    node index.js
    ```
@@ -147,19 +147,19 @@ You can now test the sample app. You need to start the Node server and access it
 
 ### Test profile editing
 
-1. After you sign in, select **Edit profile**. 
-1. Enter new changes as required, and then select **Continue**. You should see the page with sign-in status with the new changes, such as **Given Name**. 
+1. After you sign in, select **Edit profile**.
+1. Enter new changes as required, and then select **Continue**. You should see the page with sign-in status with the new changes, such as **Given Name**.
 
 ### Test password reset
 
-1. After you sign in, select **Reset password**. 
+1. After you sign in, select **Reset password**.
 1. In the next dialog that appears, you can cancel the operation by selecting **Cancel**. Alternatively, enter your email address, and then select **Send verification code**. You'll receive a verification code to your email account. Copy the verification code in your email, enter it into the password reset dialog, and then select **Verify code**.
 1. Select **Continue**.
 1. Enter your new password, confirm it, and then select **Continue**. You should see the page that shows sign-in status.
 
 ### Test sign-out
 
-After you sign in, select **Sign out**. You should see the page that has a **Sign in** button. 
+After you sign in, select **Sign out**. You should see the page that has a **Sign in** button.
 
 ## Next steps
 

articles/active-directory-b2c/configure-tokens.md

@@ -6,12 +6,10 @@ manager: CelesteDG
 ms.service: active-directory
 ms.topic: how-to
 ms.date: 01/11/2024
-ms.custom: 
 ms.author: kengaderdus
 ms.subservice: B2C
 zone_pivot_groups: b2c-policy-type
 
-
 #Customer intent: As a developer configuring token lifetimes in Azure Active Directory B2C, I want to understand the options and settings available for token lifetime and compatibility, so that I can customize them to fit the needs of my application and ensure secure access to resources.
 
 ---

articles/active-directory-b2c/configure-user-input.md

@@ -2,15 +2,11 @@
 title: Add user attributes and customize user input 
 titleSuffix: Azure AD B2C
 description: Learn how to customize user input and add user attributes to the sign-up or sign-in journey in Azure Active Directory B2C.
-
 author: garrodonnell
 manager: CelesteDG
-
 ms.service: active-directory
-
 ms.topic: how-to
 ms.date: 12/13/2023
-ms.custom: 
 ms.author: godonnell
 ms.subservice: B2C
 zone_pivot_groups: b2c-policy-type

articles/active-directory-b2c/enable-authentication-python-web-app.md

@@ -1,13 +1,13 @@
 ---
 title: Enable authentication in your own Python web application using Azure Active Directory B2C
-description: This article explains how to enable authentication in your own Python web application using Azure AD B2C 
+description: This article explains how to enable authentication in your own Python web application using Azure AD B2C
 titleSuffix: Azure AD B2C
 
 author: kengaderdus
 manager: CelesteDG
 ms.service: active-directory
 
-ms.custom: devx-track-python, devx-track-linux
+ms.custom: devx-track-python, linux-related-content
 ms.topic: how-to
 ms.date: 01/11/2024
 ms.author: kengaderdus
@@ -38,24 +38,24 @@ This article uses [Python 3.9+](https://www.python.org/) and [Flask 2.1](https:/
 1. On your file system, create a project folder for this tutorial, such as  `my-python-web-app`.
 1. In your terminal, change directory into your Python app folder, such as `cd my-python-web-app`.
 1. Run the following command to create and activate a virtual environment named `.venv` based on your current interpreter.
-    
-    # [Linux](#tab/linux)    
-    
+
+    # [Linux](#tab/linux)
+
     ```bash
     sudo apt-get install python3-venv  # If needed
     python3 -m venv .venv
     source .venv/bin/activate
     ```
 
     # [macOS](#tab/macos)
-    
+
     ```zsh
     python3 -m venv .venv
     source .venv/bin/activate
     ```
-    
+
     # [Windows](#tab/windows)
-    
+
     ```cmd
     py -3 -m venv .venv
     .venv\scripts\activate
@@ -66,24 +66,24 @@ This article uses [Python 3.9+](https://www.python.org/) and [Flask 2.1](https:/
 
     ```
     python -m pip install --upgrade pip
-    ``` 
+    ```
 
 1. To enable the Flask debug features, switch Flask to the development environment to `development` mode. For more information about debugging Flask apps, check out the [Flask documentation](https://flask.palletsprojects.com/en/2.1.x/config/#environment-and-debug-features).
 
-    # [Linux](#tab/linux)    
-    
+    # [Linux](#tab/linux)
+
     ```bash
     export FLASK_ENV=development
     ```
 
     # [macOS](#tab/macos)
-    
+
     ```zsh
     export FLASK_ENV=development
     ```
-    
+
     # [Windows](#tab/windows)
-    
+
     ```cmd
     set FLASK_ENV=development
     ```
@@ -108,7 +108,7 @@ msal>=1.7,<2
 
 In your terminal, install the dependencies by running the following commands:
 
-# [Linux](#tab/linux)    
+# [Linux](#tab/linux)
 
 ```bash
 python -m pip install -r requirements.txt
@@ -128,9 +128,9 @@ py -m pip install -r requirements.txt
 
 ---
 
-## Step 3: Build app UI components 
+## Step 3: Build app UI components
 
-Flask is a lightweight Python framework for web applications that provides the basics for URL routing and page rendering. It leverages Jinja2 as its template engine to render the content of your app. For more information, check out the [template designer documentation](https://jinja.palletsprojects.com/en/3.1.x/templates/). In this section, you add the required templates that provide the basic functionality of your web app.  
+Flask is a lightweight Python framework for web applications that provides the basics for URL routing and page rendering. It leverages Jinja2 as its template engine to render the content of your app. For more information, check out the [template designer documentation](https://jinja.palletsprojects.com/en/3.1.x/templates/). In this section, you add the required templates that provide the basic functionality of your web app.
 
 ### Step 3.1 Create a base template
 
@@ -200,28 +200,28 @@ Add the following templates under the templates folder. These templates extend t
     {% extends "base.html" %}
     {% block title %}Home{% endblock %}
     {% block content %}
-    
+
     <h1>Microsoft Identity Python Web App</h1>
-    
+
     {% if user %}
     <h2>Claims:</h2>
     <pre>{{ user |tojson(indent=4) }}</pre>
-    
-    
+
+
     {% if config.get("ENDPOINT") %}
     <li><a href='/graphcall'>Call Microsoft Graph API</a></li>
     {% endif %}
-    
+
     {% if config.get("B2C_PROFILE_AUTHORITY") %}
     <li><a href='{{_build_auth_code_flow(authority=config["B2C_PROFILE_AUTHORITY"])["auth_uri"]}}'>Edit Profile</a></li>
     {% endif %}
-    
+
     <li><a href="/logout">Logout</a></li>
-    
+
     {% else %}
     <li><a href='{{ auth_url }}'>Sign In</a></li>
     {% endif %}
-    
+
     {% endblock %}
     ```
 
@@ -243,22 +243,22 @@ Add the following templates under the templates folder. These templates extend t
     ```html
     {% extends "base.html" %}
     {% block title%}Error{% endblock%}
-    
+
     {% block metadata %}
     {% if config.get("B2C_RESET_PASSWORD_AUTHORITY") and "AADB2C90118" in result.get("error_description") %}
     <!-- See also https://learn.microsoft.com/azure/active-directory-b2c/active-directory-b2c-reference-policies#linking-user-flows -->
     <meta http-equiv="refresh"
       content='0;{{_build_auth_code_flow(authority=config["B2C_RESET_PASSWORD_AUTHORITY"])["auth_uri"]}}'>
     {% endif %}
     {% endblock %}
-    
+
     {% block content %}
     <h2>Login Failure</h2>
     <dl>
       <dt>{{ result.get("error") }}</dt>
       <dd>{{ result.get("error_description") }}</dd>
     </dl>
-    
+
     <a href="{{ url_for('index') }}">Homepage</a>
     {% endblock %}
     ```
@@ -290,7 +290,7 @@ B2C_PROFILE_AUTHORITY = authority_template.format(
 B2C_RESET_PASSWORD_AUTHORITY = authority_template.format(
     tenant=b2c_tenant, user_flow=resetpassword_user_flow)
 
-REDIRECT_PATH = "/getAToken"  
+REDIRECT_PATH = "/getAToken"
 
 # This is the API resource endpoint
 ENDPOINT = '' # Application ID URI of app registration in Azure portal
@@ -423,7 +423,7 @@ if __name__ == "__main__":
 
 In the Terminal, run the app by entering the following command, which runs the Flask development server. The development server looks for `app.py` by default. Then, open your browser and navigate to the web app URL: `http://localhost:5000`.
 
-# [Linux](#tab/linux)    
+# [Linux](#tab/linux)
 
 ```bash
 python -m flask run --host localhost --port 5000