Merge pull request #230286 from MicrosoftGuyJFlo/AADPortalBulk2

[Azure AD] AAD Portal Bulk 2

Author: v-shils

articles/active-directory/fundamentals/recover-from-deletions.md

@@ -69,7 +69,7 @@ Users enter the soft-delete state anytime the user object is deleted by using th
 
 The most frequent scenarios for user deletion are:
 
-* An administrator intentionally deletes a user in the Azure AD portal in response to a request or as part of routine user maintenance.
+* An administrator intentionally deletes a user in the Azure portal in response to a request or as part of routine user maintenance.
 * An automation script in Microsoft Graph or PowerShell triggers the deletion. For example, you might have a script that removes users who haven't signed in for a specified time.
 * A user is moved out of scope for synchronization with Azure AD Connect.
 * A user is removed from an HR system and is deprovisioned via an automated workflow.

articles/active-directory/fundamentals/recover-from-misconfigurations.md

@@ -115,7 +115,7 @@ Conditional Access policies are created on the **Conditional Access** page in th
 
 ### User and password reset configuration changes
 
-User settings changes are made on the Azure AD portal **User settings** page. Password reset changes are made on the **Password reset** page. Changes made on these pages are captured in the Audit log as detailed in the following table.
+User settings changes are made on the Azure portal **User settings** page. Password reset changes are made on the **Password reset** page. Changes made on these pages are captured in the Audit log as detailed in the following table.
 
 | Service filter| Activities| Potential impacts |
 | - | - | - |
@@ -129,7 +129,7 @@ User settings changes are made on the Azure AD portal **User settings** page. Pa
 
 ### External identities configuration changes
 
-You can make changes to these settings on the **External identities** or **External collaboration** settings pages in the Azure AD portal.
+You can make changes to these settings on the **External identities** or **External collaboration** settings pages in the Azure portal.
 
 | Service filter| Activities| Potential impacts |
 | - | - | - |

articles/active-directory/fundamentals/recoverability-overview.md

@@ -33,7 +33,7 @@ Deletions and misconfigurations have different impacts on your tenant.
 
 The impact of deletions depends on the object type.
 
-Users, Microsoft 365 Groups, and applications can be soft deleted. Soft-deleted items are sent to the Azure AD recycle bin. While in the recycle bin, items aren't available for use. However, they retain all their properties and can be restored via a Microsoft Graph API call or in the Azure AD portal. Items in the soft-delete state that aren't restored within 30 days are permanently, or hard, deleted.
+Users, Microsoft 365 Groups, and applications can be soft deleted. Soft-deleted items are sent to the Azure AD recycle bin. While in the recycle bin, items aren't available for use. However, they retain all their properties and can be restored via a Microsoft Graph API call or in the Azure portal. Items in the soft-delete state that aren't restored within 30 days are permanently, or hard, deleted.
 
 ![Diagram that shows that users, Microsoft 365 Groups, and applications are soft deleted and then hard deleted after 30 days.](media/recoverability/overview-deletes.png)
 

articles/active-directory/fundamentals/secure-with-azure-ad-resource-management.md

@@ -319,7 +319,7 @@ When a requirement exists to deploy IaaS workloads to Azure that require identit
 
 **Network Requirements**: These virtual machines will need to access Azure AD for authentication so you must ensure that the virtual machines network configuration permits outbound access to Azure AD endpoints on 443. See the documentation for [Windows](../devices/howto-vm-sign-in-azure-ad-windows.md) and [Linux](../devices/howto-vm-sign-in-azure-ad-linux.md) for more information.
 
-**Role-based Access Control (RBAC)**: Two RBAC roles are available to provide the appropriate level of access to these virtual machines. These RBAC roles can be configured via the Azure AD Portal or via the Azure Cloud Shell Experience. For more information, see [Configure role assignments for the VM](../devices/howto-vm-sign-in-azure-ad-windows.md).
+**Role-based Access Control (RBAC)**: Two RBAC roles are available to provide the appropriate level of access to these virtual machines. These RBAC roles can be configured via the Azure portal or via the Azure Cloud Shell Experience. For more information, see [Configure role assignments for the VM](../devices/howto-vm-sign-in-azure-ad-windows.md).
 
 * **Virtual machine administrator logon**: Users with this role assigned to them can log into an Azure virtual machine with administrator privileges.
 

articles/active-directory/fundamentals/service-accounts-governing-azure.md

@@ -94,7 +94,7 @@ Monitor your service accounts to ensure usage patterns are correct, and that the
 
 Use one of the following monitoring methods:
 
-* Azure AD Sign-In Logs in the Azure AD portal
+* Azure AD Sign-In Logs in the Azure portal
 * Export the Azure AD Sign-In Logs to 
   * [Azure Storage documentation](../../storage/index.yml)
   * [Azure Event Hubs documentation](../../event-hubs/index.yml), or 

articles/active-directory/governance/configure-logic-app-lifecycle-workflows.md

@@ -202,7 +202,7 @@ To configure those you'll follow these steps:
 
 1. Select Save.    
 
-1. For Logic Apps authorization policy, we'll need the managed identities **Application ID**. Since the Azure portal only shows the Object ID, we need to look up the Application ID. You can search for the managed identity by Object ID under **Enterprise Applications in the Azure AD Portal** to find the required Application ID.
+1. For Logic Apps authorization policy, we'll need the managed identities **Application ID**. Since the Azure portal only shows the Object ID, we need to look up the Application ID. You can search for the managed identity by Object ID under **Enterprise Applications in the Azure portal** to find the required Application ID.
 
 1. Go back to the logic app you created, and select **Authorization**.
 

articles/active-directory/governance/deploy-access-reviews.md

@@ -276,7 +276,7 @@ Group owners review membership because they're best qualified to know who needs
 
    For example, Microsoft Teams uses Microsoft 365 Groups as the underlying authorization model to grant users access to resources that are in SharePoint, Exchange, OneNote, or other Microsoft 365 services. The creator of the team automatically becomes an owner and should be responsible for attesting to the membership of that group.
 
-* Groups created manually in the Azure AD portal or via scripting through Microsoft Graph might not necessarily have owners defined. Define them either through the Azure AD portal in the group's **Owners** section or via Microsoft Graph.
+* Groups created manually in the Azure portal or via scripting through Microsoft Graph might not necessarily have owners defined. Define them either through the Azure portal in the group's **Owners** section or via Microsoft Graph.
 
 * Groups that are synchronized from on-premises Active Directory can't have an owner in Azure AD. When you create an access review for them, select individuals who are best suited to decide on membership in them.
 

articles/active-directory/governance/perform-access-review.md

@@ -119,7 +119,7 @@ If you're the second-stage or third-stage reviewer, you'll also see the decision
 Approve or deny access as outlined in [Review access for one or more users](#review-access-for-one-or-more-users).
 
 > [!NOTE]
-> The next stage of the review won't become active until the duration specified during the access review setup has passed. If the administrator believes a stage is done but the review duration for this stage has not expired yet, they can use the **Stop current stage** button in the overview of the access review in the Azure AD portal. This action will close the active stage and start the next stage.
+> The next stage of the review won't become active until the duration specified during the access review setup has passed. If the administrator believes a stage is done but the review duration for this stage has not expired yet, they can use the **Stop current stage** button in the overview of the access review in the Azure portal. This action will close the active stage and start the next stage.
 
 ### Review access for B2B direct connect users in Teams shared channels and Microsoft 365 groups (preview)
 

articles/active-directory/hybrid/how-to-connect-health-adfs-risky-ip-workbook.md

@@ -37,7 +37,7 @@ Additionally, it is possible for a single IP address to attempt multiple logins
 2.	A Log Analytics Workspace with the “ADFSSignInLogs” stream enabled.
 3.	Permissions to use the Azure AD Monitor Workbooks. To use Workbooks, you need:
 - An Azure Active Directory tenant with a premium (P1 or P2) license.
-- Access to a Log Analytics Workspace and the following roles in Azure AD (if accessing Log Analytics through Azure AD portal): Security administrator, Security reader, Reports reader, Global administrator
+- Access to a Log Analytics Workspace and the following roles in Azure AD (if accessing Log Analytics through Azure portal): Security administrator, Security reader, Reports reader, Global administrator
 
 
 ## What is in the report?

articles/active-directory/hybrid/how-to-connect-install-multiple-domains.md

@@ -80,7 +80,7 @@ c:[Type == "http://schemas.xmlsoap.org/claims/UPN"] => issue(Type = "http://sche
 ## How to update the trust between AD FS and Azure AD
 If you did not set up the federated trust between AD FS and your instance of Azure AD, you may need to re-create this trust.  The reason is, when it is originally set up without the `-SupportMultipleDomain` parameter, the IssuerUri is set with the default value.  In the screenshot below, you can see the IssuerUri is set to `https://adfs.bmcontoso.com/adfs/services/trust`.
 
-If you have successfully added a new domain in the Azure AD portal and then attempt to convert it using `Convert-MsolDomaintoFederated -DomainName <your domain>`, you will get the following error.
+If you have successfully added a new domain in the Azure portal and then attempt to convert it using `Convert-MsolDomaintoFederated -DomainName <your domain>`, you will get the following error.
 
 ![Screenshot that shows a federation error in PowerShell after attempting to convert a new domain with the "Convert-MsolDomaintoFederated" command.](./media/how-to-connect-install-multiple-domains/trust1.png)