[BULK] DocuTune - Updates to Azure AD rebranding g

Author: alexbuckgit

articles/logic-apps/azure-arc-enabled-logic-apps-create-deploy-workflows.md

@@ -53,24 +53,24 @@ This section describes the common prerequisites across all the approaches and to
   - [Set up an Azure Arc-enabled Kubernetes cluster to run App Service, Functions, and Logic Apps (Preview)](../app-service/manage-create-arc-environment.md)
   - [Change the default scaling behavior](#change-scaling)
 
-- Your own Azure Active Directory (Azure AD) identity
+- Your own Microsoft Entra identity
 
-  If your workflows need to use any Azure-hosted connections, such as Office 365 Outlook or Azure Storage, your logic app must use an Azure AD identity for authentication. Azure Arc-enabled Logic Apps can run on any infrastructure but requires an identity that has permissions to use Azure-hosted connections. To set up this identity, create an app registration in Azure AD that your logic app uses as the required identity.
+  If your workflows need to use any Azure-hosted connections, such as Office 365 Outlook or Azure Storage, your logic app must use a Microsoft Entra identity for authentication. Azure Arc-enabled Logic Apps can run on any infrastructure but requires an identity that has permissions to use Azure-hosted connections. To set up this identity, create an app registration in Microsoft Entra ID that your logic app uses as the required identity.
 
   > [!NOTE]
   > Managed identity support is currently unavailable for Azure Arc-enabled Logic Apps.
 
-  To create an Azure Active Directory (Azure AD) app registration using the Azure CLI, follow these steps:
+  To create a Microsoft Entra app registration using the Azure CLI, follow these steps:
 
   1. Create an app registration by using the [`az ad sp create`](/cli/azure/ad/sp#az-ad-sp-create) command.
 
   1. To review all the details, run the [`az ad sp show`](/cli/azure/ad/sp#az-ad-sp-show) command.
 
   1. From the output of both commands, find and save the client ID, object ID, tenant ID, and client secret values, which you need to keep for later use.
 
-  To create an Azure Active Directory (Azure AD) app registration using the Azure portal, follow these steps:
+  To create a Microsoft Entra app registration using the Azure portal, follow these steps:
 
-  1. Create a new Azure AD app registration by using the [Azure portal](../active-directory/develop/quickstart-register-app.md).
+  1. Create a new Microsoft Entra app registration by using the [Azure portal](../active-directory/develop/quickstart-register-app.md).
 
   1. After creation finishes, find the new app registration in the portal.
 
@@ -283,9 +283,9 @@ You can create, deploy, and monitor your logic app workflows from end to end in
 
    1. Select or create a new Application Insights resource for storing application logs for your logic app.
 
-   1. If you haven't done so, set up your Azure Active Directory (Azure AD) identity so that your logic app can authenticate managed API connections. For more information, see the top-level [Prerequisites](#prerequisites).
+   1. If you haven't done so, set up your Microsoft Entra identity so that your logic app can authenticate managed API connections. For more information, see the top-level [Prerequisites](#prerequisites).
 
-   1. Enter the client ID, tenant ID, object ID, and client secret for your Azure AD identity.
+   1. Enter the client ID, tenant ID, object ID, and client secret for your Microsoft Entra identity.
 
       > [!NOTE]
       > You only have to complete this step once. Visual Studio Code updates your project's 
@@ -316,9 +316,9 @@ The portal-based designer's editing capability is currently under development fo
 
 Currently, Azure Arc-enabled Kubernetes clusters don't support using a logic app's managed identity to authenticate managed API connections. You create these Azure-hosted and managed connections when you use managed connectors in your workflows.
 
-Instead, you have to create your own app registration in Azure Active Directory (Azure AD). You can then use this app registration as an identity for logic apps deployed and running in Azure Arc-enabled Logic Apps. For more information, review the [top-level prerequisites](#prerequisites).
+Instead, you have to create your own app registration in Microsoft Entra ID. You can then use this app registration as an identity for logic apps deployed and running in Azure Arc-enabled Logic Apps. For more information, review the [top-level prerequisites](#prerequisites).
 
-From your app registration, you need the client ID, object ID, tenant ID, and client secret. If you use Visual Studio Code to deploy, you have a built-in experience for setting up your logic app with an Azure AD identity. For more information, review [Create and deploy logic app workflows - Visual Studio Code](#create-and-deploy-logic-apps).
+From your app registration, you need the client ID, object ID, tenant ID, and client secret. If you use Visual Studio Code to deploy, you have a built-in experience for setting up your logic app with a Microsoft Entra identity. For more information, review [Create and deploy logic app workflows - Visual Studio Code](#create-and-deploy-logic-apps).
 
 However, if you use Visual Studio Code for development, but you use Azure CLI or automated pipelines to deploy, follow these steps.
 
@@ -367,8 +367,8 @@ In your Azure Resource Manager template (ARM template), include the following re
 | Parameter | Description |
 |-----------|-------------|
 | <*connection-name*> | The name for your managed API connection, for example `office365` |
-| <*object-ID*> | The object ID for your Azure AD identity, previously saved from your app registration |
-| <*tenant-ID*> | The tenant ID for your Azure AD identity, previously saved from your app registration |
+| <*object-ID*> | The object ID for your Microsoft Entra identity, previously saved from your app registration |
+| <*tenant-ID*> | The tenant ID for your Microsoft Entra identity, previously saved from your app registration |
 |||
 
 ```json

articles/logic-apps/biztalk-server-to-azure-integration-services-overview.md

@@ -566,7 +566,7 @@ BizTalk includes [Enterprise Single Sign-On (SSO)](/biztalk/core/enterprise-sing
 
 - Managed identities
 
-  Some connectors support using a [managed identity](../active-directory/managed-identities-azure-resources/overview.md) for authenticating access to resources protected by Azure Active Directory (Azure AD). When you use a managed identity to authenticate your connection, you don't have to provide credentials, secrets, or Azure AD tokens.
+  Some connectors support using a [managed identity](../active-directory/managed-identities-azure-resources/overview.md) for authenticating access to resources protected by Microsoft Entra ID. When you use a managed identity to authenticate your connection, you don't have to provide credentials, secrets, or Microsoft Entra tokens.
 
 ### Application management and access management
 
@@ -837,7 +837,7 @@ For the latest information, see [Service Bus Premium and Standard messaging tier
 
 Azure API Management offers various pricing tiers so that you can choose the best tier that meets your needs. Each tier has its own capabilities and are named Consumption, Developer, Basic, Standard, and Premium.
 
-The capabilities in these tiers range from Azure AD integration, Azure virtual network support, built-in cache, self-hosted gateways, and more. For more information about these tiers and their capabilities, see [Feature-based comparison of the Azure API Management tiers](../api-management/api-management-features.md).
+The capabilities in these tiers range from Microsoft Entra integration, Azure virtual network support, built-in cache, self-hosted gateways, and more. For more information about these tiers and their capabilities, see [Feature-based comparison of the Azure API Management tiers](../api-management/api-management-features.md).
 
 ##### Azure Data Factory
 
@@ -919,7 +919,7 @@ The following table and diagram roughly show how resources, artifacts, features,
 | EDI | - BizTalk Server out-of-the-box capabilities <br>- Parties, partners, agreements, AS2, X12, EDIFACT | Azure Logic Apps and Azure Integration Account (partners, agreements, AS2, X12, EDIFACT) |
 | HL7, RosettaNet, and SWIFT | BizTalk Server accelerators for HL7, RosettaNet, and SWIFT | - Azure Logic Apps, RosettaNet and SWIFT connectors, and Azure Integration Account <br>- Azure API Management for FHIR (HL7) <br>- Azure Blueprint, which enables SWIFT CSP compliance on Azure |
 | Secrets | Enterprise Single Sign-On (SSO) | - Azure Key Vault <br>- SQL Server <br>- Application configuration |
-| Security and governance | - Enterprise Single Sign-On (SSO) <br>- SSO affiliate applications <br>- Active Directory <br>- Signing certificates <br>- IIS Security Authentication <br>- Network security | - Azure Active Directory <br>- Azure Network Security <br>- Azure role-based access control (Azure RBAC) <br>- Claims, tokens <br>- Shared Access Policies |
+| Security and governance | - Enterprise Single Sign-On (SSO) <br>- SSO affiliate applications <br>- Active Directory <br>- Signing certificates <br>- IIS Security Authentication <br>- Network security | - Microsoft Entra ID <br>- Azure Network Security <br>- Azure role-based access control (Azure RBAC) <br>- Claims, tokens <br>- Shared Access Policies |
 | Data configuration | - Config files <br>- Enterprise SSO application configuration <br>- Custom cache components <br>- Custom database <br>- Business Rules Engine <br>- Windows registry | - Azure Key Vault <br>- Azure App Configuration <br>- Azure Cosmos DB <br>- Azure Table Storage <br>- Azure Logic Apps (Standard) configuration <br>- Azure Functions configuration <br>- Azure API Management named values and backends <br>- SQL Server <br>- Custom caching <br>- Custom database |
 | Deployment | - BizTalk Server binding file | - Azure DevOps pipelines <br>- Bicep scripts <br>- Terraform |
 | Tracking | - BizTalk Server tracking capabilities (Receive ports, Send ports, pipelines, orchestrations) <br>- IIS tracking <br>- Azure API Management built-in analytics (hybrid capabilities) | - Azure Logic Apps run  history and tracked properties <br>- Azure Storage Account <br>- Azure Monitor (Application Insights) <br>- Azure API Management built-in analytics <br>- Custom solution, for example, Azure Event Hubs plus Azure Functions plus SQL Server plus Azure Data Explorer |

articles/logic-apps/block-connections-across-tenants.md

@@ -1,12 +1,12 @@
 ---
 title: Block access to and from other tenants
-description: Block connections between your tenant and other Azure Active Directory (Azure AD) tenants in Azure Logic Apps.
+description: Block connections between your tenant and other Microsoft Entra tenants in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
 ms.date: 08/01/2022
-# Customer intent: As a developer, I want to prevent access to and from other Azure Active Directory tenants.
+# Customer intent: As a developer, I want to prevent access to and from other Microsoft Entra tenants.
 ---
 
 # Block connections to and from other tenants in Azure Logic Apps (Preview)
@@ -15,11 +15,11 @@ ms.date: 08/01/2022
 > This capability is in preview and is subject to the 
 > [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
-Azure Logic Apps includes many connectors for you to build integration apps and workflows and to access various data, apps, services, systems, and other resources. These connectors authorize your access to these resources by using Azure Active Directory (Azure AD) to authenticate your credentials.
+Azure Logic Apps includes many connectors for you to build integration apps and workflows and to access various data, apps, services, systems, and other resources. These connectors authorize your access to these resources by using Microsoft Entra ID to authenticate your credentials.
 
-When you create a connection from your workflow to access a resource, you can share that connection with others in the same Azure AD tenant or different tenant by sending a consent link. This shared connection provides access to same resource but creates a security vulnerability.
+When you create a connection from your workflow to access a resource, you can share that connection with others in the same Microsoft Entra tenant or different tenant by sending a consent link. This shared connection provides access to same resource but creates a security vulnerability.
 
-As a security measure to prevent this scenario, you can block access to and from your own Azure AD tenant through such shared connections. You can also permit but restrict connections only to specific tenants. By setting up a tenant isolation policy, you can better control data movement between your tenant and resources that require Azure AD authorized access.
+As a security measure to prevent this scenario, you can block access to and from your own Microsoft Entra tenant through such shared connections. You can also permit but restrict connections only to specific tenants. By setting up a tenant isolation policy, you can better control data movement between your tenant and resources that require Microsoft Entra authorized access.
 
 ## Prerequisites
 
@@ -31,7 +31,7 @@ As a security measure to prevent this scenario, you can block access to and from
 
 - Collect the following information:
 
-  - The tenant ID for your Azure AD tenant.
+  - The tenant ID for your Microsoft Entra tenant.
 
   - The choice whether to enforce two-way tenant isolation for connections that don't have a client tenant ID.
 
@@ -47,7 +47,7 @@ As a security measure to prevent this scenario, you can block access to and from
 
     - The choice whether to allow outbound connections from your tenant to each allowed tenant.
 
-- To test the tenant isolation policy, you need a second Azure AD tenant. From this tenant, you'll try connecting to and from the isolated tenant after the isolation policy takes effect.
+- To test the tenant isolation policy, you need a second Microsoft Entra tenant. From this tenant, you'll try connecting to and from the isolated tenant after the isolation policy takes effect.
 
 ## Request an isolation policy for your tenant
 
@@ -68,7 +68,7 @@ After the policy takes effect in a region, test the policy. You can try immediat
 
 ### Test inbound connections to your tenant
 
-1. Sign in to your "other" Azure AD tenant.
+1. Sign in to your "other" Microsoft Entra tenant.
 
 1. Create logic app workflow with a connection, such as Office 365 Outlook.
 

articles/logic-apps/block-connections-connectors.md

@@ -286,7 +286,7 @@ For more information about Azure Policy definitions, see these topics:
 
 ## Create policy assignment
 
-Next, you need to assign the policy definition where you want to enforce the policy, for example, to a single resource group, multiple resource groups, Azure Active Directory (Azure AD) tenant, or Azure subscription. For this task, follow these steps to create a policy assignment:
+Next, you need to assign the policy definition where you want to enforce the policy, for example, to a single resource group, multiple resource groups, Microsoft Entra tenant, or Azure subscription. For this task, follow these steps to create a policy assignment:
 
 1. In the [Azure portal](https://portal.azure.com), portal search box, enter **policy**, and select **Policy**.