Merge pull request #88 from AlexaCRM/renameAAD

rename AAD
AlexaCRM · Nov 6, 2024 · 5c522c0 · 5c522c0
2 parents 417d2e5 + 682f54f
commit 5c522c0
Show file tree

Hide file tree

Showing 4 changed files with 13 additions and 13 deletions.
diff --git a/datapress/getting-started.md b/datapress/getting-started.md
@@ -36,12 +36,12 @@ Dataverse / Dynamics 365 supports several deployment and authentication scenario
 
 To create application id and client secret or certificate you need to complete the following steps:
 
-1. [Register an app](https://docs.microsoft.com/azure/active-directory/develop/quickstart-register-app#register-an-application) in Azure Active Directory. During the registration select **Accounts in this organizational directory only** as Supported account types. Stop the walkthrough after the step when the app is registered, do not add redirect URI or change platform settings. Copy Application (client) ID and set it aside.
-2. [Add client secret credentials](https://docs.microsoft.com/azure/active-directory/develop/quickstart-register-app#add-credentials). You can use either client secret or certificate. If using the secret make sure to copy and set it aside. If using certificate, make sure you have a certificate file (.cer) and its password protected copy (.pfx).
+1. [Register an app](https://learn.microsoft.com/entra/identity-platform/quickstart-register-app?tabs=certificate#register-an-application) in Microsoft Entra ID. During the registration select **Accounts in this organizational directory only** as Supported account types. Stop the walkthrough after the step when the app is registered, do not add redirect URI or change platform settings. Copy Application (client) ID and set it aside.
+2. [Add client secret credentials](https://learn.microsoft.com/entra/identity-platform/quickstart-register-app?tabs=certificate#add-credentials). You can use either client secret or certificate. If using the secret make sure to copy and set it aside. If using certificate, make sure you have a certificate file (.cer) and its password protected copy (.pfx).
 3. Create an application user in Dataverse by following [these instructions](https://docs.microsoft.com/power-platform/admin/manage-application-users#create-an-application-user). Make sure to [assign security roles](https://docs.microsoft.com/power-platform/admin/manage-application-users#manage-roles-for-an-application-user) to the user. We recommend assigning **Basis User** built-in role or another role with same or wider privileges. If you have the WordPress solution installed in your Dataverse instance, assign **WordPress App User** role to the app user. This security role provides access to additional tables included with the solution, for example **WordPress Sites**.
 4. If you have the WordPress solution installed, add the app user to **WordPress Site Password** column security profile. This [column level security](https://learn.microsoft.com/power-platform/admin/field-level-security) ensures that the app user has access to the secure columns included with the solution, even without system administrator privileges.  
 
-You can also use [Azure CLI](https://learn.microsoft.com/en-us/cli/azure/install-azure-cli) (command line interface) to create app user and secret. 
+You can also use [Azure CLI](https://learn.microsoft.com/cli/azure/install-azure-cli) (command line interface) to create app user and secret. 
 
 1. `az login --user <[email protected]> --password <myPassword>` to login to Microsoft Azure. 
 

diff --git a/wpcrm/configuration.md b/wpcrm/configuration.md
@@ -37,22 +37,22 @@ Dynamics CRM Address
 : Absolute URL to your Microsoft Dynamics CRM, e. g. `https://contoso.crm.dynamics.com` for CRM Online, or `https://crm.example.net` for the on-premises deployment.
 
 Application ID
-: Azure AD application registration identifier. The app user mapped to this registration will be used to authenticate and access the CRM data, please ensure that the user has sufficient permissions to access Dynamics CRM.
+: Microsoft Entra ID application registration identifier. The app user mapped to this registration will be used to authenticate and access the CRM data, please ensure that the user has sufficient permissions to access Dynamics CRM.
 
 Client Secret
- Application registration secret as defined in Azure AD. Make sure the secret has not expired.
+ Application registration secret as defined in Microsoft Entra ID. Make sure the secret has not expired.
 
 Step-by-step instructions how to create app id and secret are available in [this knowledge base article](https://alexacrm.com/kb/plugin/config/oauth-setup/).
 
 ### Using the exact specified STS URL
 
 **TL;DR:** Check this box if you are using federated authentication and running into connection problems.
 
-For Online deployments you may notice another setting, **Federated login only: use the exact specified STS URL.** In scenarios with federated authentication, the plugin first makes a request to Azure AD to determine the federated STS URL. Most commonly it points to the UsernameMixed endpoint in ADFS. 
+For Online deployments you may notice another setting, **Federated login only: use the exact specified STS URL.** In scenarios with federated authentication, the plugin first makes a request to Microsoft Entra ID to determine the federated STS URL. Most commonly it points to the UsernameMixed endpoint in ADFS. 
 
-However, in some cases an unsupported ADFS endpoint may be specified by Azure AD, or non-ADFS integration may be employed. The default behavior for the plugin is to use the specified domain and the hard-coded endpoint, `/adfs/services/trust/13/usernamemixed`.
+However, in some cases an unsupported ADFS endpoint may be specified by Microsoft Entra ID, or non-ADFS integration may be employed. The default behavior for the plugin is to use the specified domain and the hard-coded endpoint, `/adfs/services/trust/13/usernamemixed`.
 
-When a non-ADFS solution is employed, or ADFS is being used in a non-supported way, such behavior may actually make things worse. For that reason, please check this box to make the plugin use the exact STS URL as reported by Azure Active Directory.
+When a non-ADFS solution is employed, or ADFS is being used in a non-supported way, such behavior may actually make things worse. For that reason, please check this box to make the plugin use the exact STS URL as reported by Microsoft Entra ID.
 
 ## Portal
 

diff --git a/wpcrm/knowledge_base/configuration/configuration.md b/wpcrm/knowledge_base/configuration/configuration.md
@@ -8,11 +8,11 @@ tags:
     - Dynamics 365 Integration
 ---
 
-IMPORTANT! To complete the steps below you need to have one of the following roles in Azure Active Directory: Dynamics 365 Administrator, Power Platform Administrator, or Global Administrator.
+IMPORTANT! To complete the steps below you need to have one of the following roles in Microsoft Entra ID: Dynamics 365 Administrator, Power Platform Administrator, or Global Administrator.
 
-**Register application in Azure Active Directory**<br></br>
+**Register application in Microsoft Entra ID**<br></br>
 1. Navigate to https://portal.azure.com in your browser.
-2. Select Azure Active Directory. If it is not available on the screen, select search bar and type azure active directory then select it from the search results.
+2. Select Microsoft Entra ID. If it is not available on the screen, select search bar and type Microsoft Entra ID then select it from the search results.
 
 ![image1](../img/azure1.png)
 

diff --git a/wpcrm/quickstart.md b/wpcrm/quickstart.md
@@ -29,8 +29,8 @@ Choose the *CRM Online* deployment type. Enter the URL of your Dynamics 365 orga
 
 If you do not have app id/secret ready then you need to complete the following steps:
 
-1. [Register an app](https://docs.microsoft.com/azure/active-directory/develop/quickstart-register-app#register-an-application) in Azure Active Directory. During the registration select **Accounts in this organizational directory only** as Supported account types. Stop the walkthrough after the step when the app is registered, do not add redirect URI or change platform settings. Copy Application (client) ID and set aside.
-2. [Add client secret credentials](https://docs.microsoft.com/azure/active-directory/develop/quickstart-register-app#add-credentials). Copy client secret and set aside.
+1. [Register an app](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app?tabs=certificate#register-an-application) in Microsoft Entra ID. During the registration select **Accounts in this organizational directory only** as Supported account types. Stop the walkthrough after the step when the app is registered, do not add redirect URI or change platform settings. Copy Application (client) ID and set aside.
+2. [Add client secret credentials](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app?tabs=certificate#add-credentials). Copy client secret and set aside.
 3. Create an application user in Dataverse by following [these instructions](https://docs.microsoft.com/power-platform/admin/manage-application-users#create-an-application-user). Make sure to [assign roles](https://docs.microsoft.com/power-platform/admin/manage-application-users#manage-roles-for-an-application-user) to the user.
 4. Use application id and client secret in the plugin configuration dialog.