From 280b157cf26d180924939cb406724f79c70382c0 Mon Sep 17 00:00:00 2001 From: dayodeji Date: Mon, 13 May 2024 17:43:01 -0400 Subject: [PATCH] Entra Rebrand --- .github/PULL_REQUEST_TEMPLATE.md | 2 +- AppCreationScripts/AppCreationScripts.md | 18 +++++++++--------- LICENSE.md | 2 +- README.md | 10 +++++----- 4 files changed, 16 insertions(+), 16 deletions(-) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index ab05e29..37ae6b1 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -42,4 +42,4 @@ Verify that the following are valid * ... ## Other Information - \ No newline at end of file + diff --git a/AppCreationScripts/AppCreationScripts.md b/AppCreationScripts/AppCreationScripts.md index 6e062df..5dc5b78 100644 --- a/AppCreationScripts/AppCreationScripts.md +++ b/AppCreationScripts/AppCreationScripts.md @@ -11,7 +11,7 @@ Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process -Force ``` -1. Run the script to create your Azure AD application and configure the code of the sample application accordingly. +1. Run the script to create your Microsoft Entra application and configure the code of the sample application accordingly. ```PowerShell cd .\AppCreationScripts\ @@ -35,23 +35,23 @@ ### Presentation of the scripts -This sample comes with two PowerShell scripts, which automate the creation of the Azure Active Directory applications, and the configuration of the code for this sample. Once you run them, you will only need to build the solution and you are good to test. +This sample comes with two PowerShell scripts, which automate the creation of the Microsoft Entra applications, and the configuration of the code for this sample. Once you run them, you will only need to build the solution and you are good to test. These scripts are: - `Configure.ps1` which: - - creates Azure AD applications and their related objects (permissions, dependencies, secrets, app roles), + - creates Microsoft Entra applications and their related objects (permissions, dependencies, secrets, app roles), - changes the configuration files in the sample projects. - - creates a summary file named `createdApps.html` in the folder from which you ran the script, and containing, for each Azure AD application it created: + - creates a summary file named `createdApps.html` in the folder from which you ran the script, and containing, for each Microsoft Entra application it created: - the identifier of the application - the AppId of the application - - the url of its registration in the [Azure portal](https://portal.azure.com). + - the url of its registration in the [Microsoft Entra admin center](https://entra.microsoft.com). -- `Cleanup.ps1` which cleans-up the Azure AD objects created by `Configure.ps1`. Note that this script does not revert the changes done in the configuration files, though. You will need to undo the change from source control (from Visual Studio, or from the command line using, for instance, `git reset`). +- `Cleanup.ps1` which cleans-up the Microsoft Entra objects created by `Configure.ps1`. Note that this script does not revert the changes done in the configuration files, though. You will need to undo the change from source control (from Visual Studio, or from the command line using, for instance, `git reset`). ### Usage pattern for tests and DevOps scenarios -The `Configure.ps1` will stop if it tries to create an Azure AD application which already exists in the tenant. For this, if you are using the script to try/test the sample, or in DevOps scenarios, you might want to run `Cleanup.ps1` just before `Configure.ps1`. This is what is shown in the steps below. +The `Configure.ps1` will stop if it tries to create a Microsoft Entra application which already exists in the tenant. For this, if you are using the script to try/test the sample, or in DevOps scenarios, you might want to run `Cleanup.ps1` just before `Configure.ps1`. This is what is shown in the steps below. ## How to use the app creation scripts? @@ -118,8 +118,8 @@ Note that the script will choose the tenant in which to create the applications, if you want to create the apps in a particular tenant, you can use the following option: -- Open the [Azure portal](https://portal.azure.com) -- Select the Azure Active directory you are interested in (in the combo-box below your name on the top right of the browser window) +- Open the [Microsoft Entra admin center](https://entra.microsoft.com) +- Select the Microsoft Entra ID you are interested in (in the combo-box below your name on the top right of the browser window) - Find the "Active Directory" object in this tenant - Go to **Properties** and copy the content of the **Directory Id** property - Then use the full syntax to run the scripts: diff --git a/LICENSE.md b/LICENSE.md index 7965606..9e841e7 100644 --- a/LICENSE.md +++ b/LICENSE.md @@ -18,4 +18,4 @@ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE - SOFTWARE \ No newline at end of file + SOFTWARE diff --git a/README.md b/README.md index b2c49a4..795177e 100644 --- a/README.md +++ b/README.md @@ -5,7 +5,7 @@ languages: products: - nodejs - ms-graph -- azure-active-directory +- microsoft-entra-id description: "Demonstrates how to use MSAL Node to acquire an access token for a protected resource such as Microsoft Graph in a console daemon application using the application's own identity (client credentials flow)" urlFragment: "ms-identity-javascript-nodejs-console" --- @@ -44,14 +44,14 @@ This sample demonstrates the following **MSAL Node** concepts: ### Setup -1. [Register a new application](https://docs.microsoft.com/azure/active-directory/develop/scenario-daemon-app-registration) in the [Azure Portal](https://portal.azure.com). +1. [Register a new application](https://docs.microsoft.com/azure/active-directory/develop/scenario-daemon-app-registration) in the [Microsoft Entra admin center](https://entra.microsoft.com). 1. For API Permissions, select `User.Read.All` under **Microsoft APIs** > **Microsoft Graph** > **Application Permissions**. 2. Select **Grant admin consent for {tenant}**. 1. Clone this repository `git clone https://github.com/Azure-Samples/ms-identity-javascript-nodejs-console.git` 1. Open the [.env](.env) file and provide the required configuration values. - 1. Replace the string `Enter_the_Tenant_Info_Here` with your tenant ID on Azure AD portal. - 2. Replace the string `Enter_the_Application_Id_Here` with your app/client ID on Azure AD portal. - 3. Replace the string `Enter_the_Client_Secret_Here` with the client secret you created on Azure AD portal. + 1. Replace the string `Enter_the_Tenant_Info_Here` with your tenant ID on Microsoft Entra admin center. + 2. Replace the string `Enter_the_Application_Id_Here` with your app/client ID on Microsoft Entra admin center. + 3. Replace the string `Enter_the_Client_Secret_Here` with the client secret you created on Microsoft Entra admin center. 4. Replace the string `Enter_the_Cloud_Instance_Id_Here` with `https://login.microsoftonline.com/` (see **note** below). 5. Replace the string `Enter_the_Graph_Endpoint_Here`. with `https://graph.microsoft.com/` (see **note** below).