Merge pull request #251648 from MicrosoftDocs/main

09/15 AM Publishing

Author: v-alje

.openpublishing.redirection.active-directory.json

@@ -5290,6 +5290,11 @@
       "redirect_url": "/azure/active-directory/reports-monitoring/howto-customize-filter-logs",
       "redirect_document_id": true
     },
+    {
+      "source_path_from_root": "/articles/active-directory/reports-monitoring/tutorial-azure-monitor-stream-logs-to-event-hub.md",
+      "redirect_url": "/azure/active-directory/reports-monitoring/howto-stream-logs-to-event-hub",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/active-directory/reports-monitoring/reference-basic-info-sign-in-logs.md",
       "redirect_url": "/azure/active-directory/reports-monitoring/concept-sign-in-log-activity-details",

.openpublishing.redirection.json

@@ -1,5 +1,10 @@
 {
     "redirections": [
+        {
+          "source_path": "articles/azure-resource-manager/bicep/bicep-import-providers.md",
+          "redirect_URL": "bicep-import",
+          "redirect_document_id": false
+        },
         {
             "source_path": "articles/migrate/tutorial-assess-webapps-physical.md",
             "redirect_URL": "tutorial-assess-webapps",
@@ -49,7 +54,7 @@
             "source_path": "articles/storsimple/storsimple-virtual-array-update-11-release-notes.md",
             "redirect_url": "/azure/storsimple/storsimple-overview",
             "redirect_document_id": false
-        },        
+        },
         {
             "source_path": "articles/storsimple/storsimple-ova-overview.md",
             "redirect_url": "/azure/storsimple/storsimple-overview",
@@ -70,7 +75,7 @@
             "redirect_url": "/azure/storsimple/storsimple-overview",
             "redirect_document_id": false
         },
-        {   
+        {
             "source_path": "articles/storsimple/storsimple-virtual-array-deploy1-portal-prep.md",
             "redirect_url": "/azure/storsimple/storsimple-overview",
             "redirect_document_id": false
@@ -9986,7 +9991,7 @@
             "source_path_from_root": "/articles/container-instances/container-instances-quotas.md",
             "redirect_url": "/azure/container-instances/container-instances-resource-and-quota-limits",
             "redirect_document_id": false
-        },    
+        },
         {
             "source_path_from_root": "/articles/container-registry/container-registry-managed-get-started-azure-cli.md",
             "redirect_url": "/azure/container-registry/container-registry-get-started-azure-cli",
@@ -14190,17 +14195,17 @@
         {
             "source_path_from_root": "/articles/load-balancer/scripts/load-balancer-linux-cli-load-balance-multiple-websites-vm.md",
             "redirect_url": "/azure/load-balancer/load-balancer-multiple-ip",
-            "redirect_document_id": false 
+            "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/load-balancer/scripts/load-balancer-linux-cli-sample-nlb.md",
             "redirect_url": "/azure/load-balancer/tutorial-multi-availability-sets-portal",
-            "redirect_document_id": false 
+            "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/load-balancer/scripts/load-balancer-linux-cli-sample-zonal-frontend.md",
             "redirect_url": "/azure/load-balancer/tutorial-load-balancer-standard-public-zonal-portal",
-            "redirect_document_id": false 
+            "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/load-balancer/scripts/load-balancer-windows-powershell-sample-nlb.md",
@@ -14691,7 +14696,7 @@
             "source_path_from_root": "/articles/notification-hubs/cross-region-recovery.md",
             "redirect_url": "/azure/notification-hubs/notification-hubs-high-availability",
             "redirect_document_id": false
-        },                
+        },
         {
             "source_path_from_root": "/articles/open-datasets/service/how-to-create-dataset-from-open-dataset.md",
             "redirect_url": "/azure/open-datasets/how-to-create-azure-machine-learning-dataset-from-open-dataset",
@@ -23952,7 +23957,7 @@
             "redirect_url": "/previous-versions/azure/virtual-machines/linux/openshift-container-platform-3x",
             "redirect_document_id": false
           },
-	    { 
+	    {
             "source_path": "articles/orbital/orbital-preview.md",
             "redirect_url": "/azure/orbital/overview",
             "redirect_document_id": false
@@ -23961,7 +23966,7 @@
             "source_path": "articles/private-multi-access-edge-compute-mec/metaswitch-fusion-core-overview.md",
             "redirect_URL": "/azure/private-5g-core",
             "redirect_document_id": false
-        },        
+        },
         {
             "source_path": "articles/private-5g-core/modify-site-plan.md",
             "redirect_URL": "/azure/private-5g-core/modify-service-plan",
@@ -24161,12 +24166,12 @@
             "source_path_from_root": "/articles/azure-functions/create-function-app-linux-app-service-plan.md",
             "redirect_url": "/azure/azure-functions/functions-create-function-app-portal",
             "redirect_document_id": false
-        },  
+        },
         {
             "source_path_from_root": "/articles/azure-functions/create-premium-plan-function-app-portal.md",
             "redirect_url": "/azure/azure-functions/functions-create-function-app-portal",
             "redirect_document_id": false
-        },       
+        },
         {
             "source_path_from_root": "/articles/sentinel/data-connectors/windows-firewall-events-via-ama.md",
             "redirect_url": "/azure/sentinel/data-connectors-reference",
@@ -24460,7 +24465,7 @@
         {
             "source_path_from_root": "/articles/virtual-machines/image-builder-reliability.md",
             "redirect_url": "/azure/reliability/reliability-image-builder.md",
-            "redirect_document_id": false 
+            "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/bastion/bastion-connect-vm-rdp-linux.md",

articles/active-directory-b2c/partner-f5.md

@@ -234,12 +234,12 @@ The BIG-IP has required Azure AD B2C requests in its preconfigured request set.
 
 | Parameter | Parameter name | Parameter value|
 |----|---|---|
-| client-id | client-id |N/A |
+| client_id | client_id |N/A |
 | nonce | nonce| N/A|
-| redirect-uri | redirect-uri | N/A|
+| redirect_uri | redirect_uri | N/A|
 | scope | scope | N/A|
-| response-type | response-type | N/A|
-| client-secret | client-secret |N/A |
+| response_type | response_type | N/A|
+| client_secret | client_secret |N/A |
 | custom | grant_type | authorization_code |
 
 **Auth redirect request: Enabled**
@@ -254,9 +254,9 @@ The BIG-IP has required Azure AD B2C requests in its preconfigured request set.
 
 | Parameter | Parameter name | Parameter value|
 |---|---|----|
-| client-id | client-id | N/A|
-| redirect-uri | redirect-uri |N/A |
-| response-type |response-type |N/A |
+| client_id | client_id | N/A|
+| redirect_uri | redirect_uri |N/A |
+| response_type |response_type |N/A |
 | scope | scope | N/A|
 | nonce | nonce | N/A|
 

articles/active-directory-domain-services/alert-ldaps.md

@@ -10,7 +10,7 @@ ms.service: active-directory
 ms.subservice: domain-services
 ms.workload: identity
 ms.topic: troubleshooting
-ms.date: 01/29/2023
+ms.date: 09/15/2023
 ms.author: justinha
 
 ---
@@ -30,7 +30,7 @@ This article helps you understand and resolve common alerts with secure LDAP acc
 
 When you enable secure LDAP, it's recommended to create additional rules that restrict inbound LDAPS access to specific IP addresses. These rules protect the managed domain from brute force attacks. To update the network security group to restrict TCP port 636 access for secure LDAP, complete the following steps:
 
-1. In the Azure portal, search for and select **Network security groups**.
+1. In the [Microsoft Entra admin center](https://entra.microsoft.com), search for and select **Network security groups**.
 1. Choose the network security group associated with your managed domain, such as *AADDS-contoso.com-NSG*, then select **Inbound security rules**
 1. Select **+ Add** to create a rule for TCP port 636. If needed, select **Advanced** in the window to create a rule.
 1. For the **Source**, choose *IP Addresses* from the drop-down menu. Enter the source IP addresses that you want to grant access for secure LDAP traffic.

articles/active-directory-domain-services/alert-nsg.md

@@ -10,7 +10,7 @@ ms.service: active-directory
 ms.subservice: domain-services
 ms.workload: identity
 ms.topic: troubleshooting
-ms.date: 01/29/2023
+ms.date: 09/15/2023
 ms.author: justinha
 
 ---
@@ -63,7 +63,7 @@ The following default inbound and outbound security rules are applied to the net
 
 To verify the existing security rules and make sure the default ports are open, complete the following steps:
 
-1. In the Azure portal, search for and select **Network security groups**.
+1. In the [Microsoft Entra admin center](https://entra.microsoft.com), search for and select **Network security groups**.
 1. Choose the network security group associated with your managed domain, such as *AADDS-contoso.com-NSG*.
 1. On the **Overview** page, the existing inbound and outbound security rules are shown.
 
@@ -75,7 +75,7 @@ To verify the existing security rules and make sure the default ports are open,
 
 To add a missing security rule, complete the following steps:
 
-1. In the Azure portal, search for and select **Network security groups**.
+1. In the [Microsoft Entra admin center](https://entra.microsoft.com), search for and select **Network security groups**.
 1. Choose the network security group associated with your managed domain, such as *AADDS-contoso.com-NSG*.
 1. Under **Settings** in the left-hand panel, click *Inbound security rules* or *Outbound security rules* depending on which rule you need to add.
 1. Select **Add**, then create the required rule based on the port, protocol, direction, etc. When ready, select **OK**.

articles/active-directory-domain-services/alert-service-principal.md

@@ -11,7 +11,7 @@ ms.subservice: domain-services
 ms.workload: identity
 ms.custom: has-azure-ad-ps-ref
 ms.topic: troubleshooting
-ms.date: 01/29/2023
+ms.date: 09/15/2023
 ms.author: justinha
 ---
 # Known issues: Service principal alerts in Azure Active Directory Domain Services
@@ -32,8 +32,7 @@ If a required service principal is deleted, the Azure platform can't perform aut
 
 To check which service principal is missing and must be recreated, complete the following steps:
 
-1. In the Azure portal, select **Azure Active Directory** from the left-hand navigation menu.
-1. Select **Enterprise applications**. Choose *All applications* from the **Application Type** drop-down menu, then select **Apply**.
+1. In the [Microsoft Entra admin center](https://entra.microsoft.com), search for and select **Enterprise applications**. Choose *All applications* from the **Application Type** drop-down menu, then select **Apply**.
 1. Search for each of the following application IDs. For Azure Global, search for AppId value *2565bd9d-da50-47d4-8b85-4c97f669dc36*. For other Azure clouds, search for AppId value *6ba9a5d4-8456-4118-b521-9c5ca10cdf84*. If no existing application is found, follow the *Resolution* steps to create the service principal or re-register the namespace.
 
     | Application ID | Resolution |
@@ -66,7 +65,7 @@ The managed domain's health automatically updates itself within two hours and re
 
 If application ID *443155a6-77f3-45e3-882b-22b3a8d431fb*, *abba844e-bc0e-44b0-947a-dc74e5d09022*, or *d87dcbc6-a371-462e-88e3-28ad15ec4e64* is missing from your Azure AD directory, complete the following steps to re-register the *Microsoft.AAD* resource provider:
 
-1. In the Azure portal, search for and select **Subscriptions**.
+1. In the [Microsoft Entra admin center](https://entra.microsoft.com), search for and select **Subscriptions**.
 1. Choose the subscription associated with your managed domain.
 1. From the left-hand navigation, choose **Resource Providers**.
 1. Search for *Microsoft.AAD*, then select **Re-register**.

articles/active-directory-domain-services/change-sku.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: domain-services
 ms.workload: identity
 ms.topic: how-to
-ms.date: 03/23/2023
+ms.date: 09/15/2023
 ms.author: justinha
 
 #Customer intent: As an identity administrator, I want to change the SKU for my Azure AD Domain Services managed domain to use different features as my business requirements change.
@@ -21,7 +21,7 @@ In Azure Active Directory Domain Services (Azure AD DS), the available performan
 
 You select a SKU when you create the managed domain, and you can switch SKUs up or down as your business needs change after the managed domain has been deployed. Changes in business requirements could include the need for more frequent backups or to create additional forest trusts. For more information on the limits and pricing of the different SKUs, see [Azure AD DS SKU concepts][concepts-sku] and [Azure AD DS pricing][pricing] pages.
 
-This article shows you how to change the SKU for an existing Azure AD DS managed domain using the Azure portal.
+This article shows you how to change the SKU for an existing Azure AD DS managed domain using the [Microsoft Entra admin center](https://entra.microsoft.com).
 
 ## Before you begin
 
@@ -44,18 +44,18 @@ For more information on these limits, see [Azure AD DS SKU features and limits][
 
 ## Select a new SKU
 
-To change the SKU for a managed domain using the Azure portal, complete the following steps:
+To change the SKU for a managed domain using the [Microsoft Entra admin center](https://entra.microsoft.com), complete the following steps:
 
-1. At the top of the Azure portal, search for and select **Azure AD Domain Services**. Choose your managed domain from the list, such as *aaddscontoso.com*.
+1. In the [Microsoft Entra admin center](https://entra.microsoft.com), search for and select **Azure AD Domain Services**. Choose your managed domain from the list, such as *aaddscontoso.com*.
 1. In the menu on the left-hand side of the Azure AD DS page, select **Settings > SKU**.
 
-    ![Select the SKU menu option for your Azure AD DS managed domain in the Azure portal](media/change-sku/overview-change-sku.png)
+    ![Select the SKU menu option for your Azure AD DS managed domain in the Microsoft Entra admin center](media/change-sku/overview-change-sku.png)
 
 1. From the drop-down menu, select the SKU you wish for your managed domain. If you have a resource forest, you can't select *Standard* SKU as forest trusts are only available on the *Enterprise* SKU or higher.
 
     Choose the SKU you want from the drop-down menu, then select **Save**.
 
-    ![Choose the required SKU from the drop-down menu in the Azure portal](media/change-sku/change-sku-selection.png)
+    ![Choose the required SKU from the drop-down menu in the Microsoft Entra admin center](media/change-sku/change-sku-selection.png)
 
 It can take a minute or two to change the SKU type.
 

articles/active-directory/app-proxy/app-proxy-protect-ndes.md

@@ -50,14 +50,14 @@ Azure AD Application Proxy is built on Azure. It gives you a massive amount of n
    * If Internet Explorer Enhanced Security Configuration is turned on for the server where you install the connector, the registration screen might be blocked. To allow access, follow the instructions in the error message, or turn off Internet Explorer Enhanced Security during the install process.
    * If connector registration fails, see [Troubleshoot Application Proxy](application-proxy-troubleshoot.md).
 1. At the end of the setup, a note is shown for environments with an outbound proxy. To configure the Azure AD Application Proxy connector to work through the outbound proxy, run the provided script, such as `C:\Program Files\Microsoft AAD App Proxy connector\ConfigureOutBoundProxy.ps1`.
-1. On the Application proxy page in the Azure portal, the new connector is listed with a status of *Active*, as shown in the following example:
+1. On the Application proxy page in the Microsoft Entra admin center, the new connector is listed with a status of *Active*, as shown in the following example:
 
-    ![The new Azure AD Application Proxy connector shown as active in the Azure portal](./media/app-proxy-protect-ndes/connected-app-proxy.png)
+    ![The new Azure AD Application Proxy connector shown as active in the Microsoft Entra admin center](./media/app-proxy-protect-ndes/connected-app-proxy.png)
 
     > [!NOTE]
     > To provide high availability for applications authenticating through the Azure AD Application Proxy, you can install connectors on multiple VMs. Repeat the same steps listed in the previous section to install the connector on other servers joined to the Azure AD DS managed domain.
 
-1. After successful installation, go back to the Azure portal.
+1. After successful installation, go back to the Microsoft Entra admin center.
 
 1. Select **Enterprise applications**.
 

articles/active-directory/app-proxy/application-proxy-add-on-premises-application.md

@@ -1,6 +1,6 @@
 ---
 title: Tutorial - Add an on-premises app - Application Proxy in Azure Active Directory
-description:  Azure Active Directory (Azure AD) has an Application Proxy service that enables users to access on-premises applications by signing in with their Azure AD account. This tutorial shows you how to prepare your environment for use with Application Proxy. Then, it uses the Azure portal to add an on-premises application to your Azure AD tenant.
+description:  Azure Active Directory (Azure AD) has an Application Proxy service that enables users to access on-premises applications by signing in with their Azure AD account. This tutorial shows you how to prepare your environment for use with Application Proxy. Then, it uses the Microsoft Entra admin center to add an on-premises application to your Azure AD tenant.
 services: active-directory
 author: kenwith
 manager: amycolannino
@@ -180,9 +180,9 @@ For information about connectors, capacity planning, and how they stay up-to-dat
 
 ## Verify the connector installed and registered correctly
 
-You can use the Azure portal or your Windows server to confirm that a new connector installed correctly.
+You can use the Microsoft Entra admin center or your Windows server to confirm that a new connector installed correctly.
 
-### Verify the installation through Azure portal
+### Verify the installation through Microsoft Entra admin center
 
 To confirm the connector installed and registered correctly:
 
@@ -219,7 +219,7 @@ Now that you've prepared your environment and installed a connector, you're read
 
     | Field  | Description |
     | :--------------------- | :----------------------------------------------------------- |
-    | **Name** | The name of the application that appears on My Apps and in the Azure portal. |
+    | **Name** | The name of the application that appears on My Apps and in the Microsoft Entra admin center. |
     | **Maintenance Mode** | Select if you would like to enable maintenance mode and temporarily disable access for all users to the application. |
     | **Internal URL** | The URL for accessing the application from inside your private network. You can provide a specific path on the backend server to publish, while the rest of the server is unpublished. In this way, you can publish different sites on the same server as different apps, and give each one its own name and access rules.<br><br>If you publish a path, make sure that it includes all the necessary images, scripts, and style sheets for your application. For example, if your app is at `https://yourapp/app` and uses images located at `https://yourapp/media`, then you should publish `https://yourapp/` as the path. This internal URL doesn't have to be the landing page your users see. For more information, see [Set a custom home page for published apps](application-proxy-configure-custom-home-page.md). |
     | **External URL** | The address for users to access the app from outside your network. If you don't want to use the default Application Proxy domain, read about [custom domains in Azure AD Application Proxy](./application-proxy-configure-custom-domain.md). |