Skip to content

Commit 280b157

Browse files
committed
Entra Rebrand
1 parent 5073ca2 commit 280b157

File tree

4 files changed

+16
-16
lines changed

4 files changed

+16
-16
lines changed

.github/PULL_REQUEST_TEMPLATE.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -42,4 +42,4 @@ Verify that the following are valid
4242
* ...
4343

4444
## Other Information
45-
<!-- Add any other helpful information that may be needed here. -->
45+
<!-- Add any other helpful information that may be needed here. -->

AppCreationScripts/AppCreationScripts.md

+9-9
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@
1111
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process -Force
1212
```
1313

14-
1. Run the script to create your Azure AD application and configure the code of the sample application accordingly.
14+
1. Run the script to create your Microsoft Entra application and configure the code of the sample application accordingly.
1515

1616
```PowerShell
1717
cd .\AppCreationScripts\
@@ -35,23 +35,23 @@
3535

3636
### Presentation of the scripts
3737

38-
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.
38+
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.
3939

4040
These scripts are:
4141

4242
- `Configure.ps1` which:
43-
- creates Azure AD applications and their related objects (permissions, dependencies, secrets, app roles),
43+
- creates Microsoft Entra applications and their related objects (permissions, dependencies, secrets, app roles),
4444
- changes the configuration files in the sample projects.
45-
- 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:
45+
- 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:
4646
- the identifier of the application
4747
- the AppId of the application
48-
- the url of its registration in the [Azure portal](https://portal.azure.com).
48+
- the url of its registration in the [Microsoft Entra admin center](https://entra.microsoft.com).
4949

50-
- `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`).
50+
- `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`).
5151

5252
### Usage pattern for tests and DevOps scenarios
5353

54-
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.
54+
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.
5555

5656
## How to use the app creation scripts?
5757

@@ -118,8 +118,8 @@ Note that the script will choose the tenant in which to create the applications,
118118
119119
if you want to create the apps in a particular tenant, you can use the following option:
120120
121-
- Open the [Azure portal](https://portal.azure.com)
122-
- Select the Azure Active directory you are interested in (in the combo-box below your name on the top right of the browser window)
121+
- Open the [Microsoft Entra admin center](https://entra.microsoft.com)
122+
- Select the Microsoft Entra ID you are interested in (in the combo-box below your name on the top right of the browser window)
123123
- Find the "Active Directory" object in this tenant
124124
- Go to **Properties** and copy the content of the **Directory Id** property
125125
- Then use the full syntax to run the scripts:

LICENSE.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,4 +18,4 @@
1818
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
1919
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
2020
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21-
SOFTWARE
21+
SOFTWARE

README.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ languages:
55
products:
66
- nodejs
77
- ms-graph
8-
- azure-active-directory
8+
- microsoft-entra-id
99
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)"
1010
urlFragment: "ms-identity-javascript-nodejs-console"
1111
---
@@ -44,14 +44,14 @@ This sample demonstrates the following **MSAL Node** concepts:
4444

4545
### Setup
4646

47-
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).
47+
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).
4848
1. For API Permissions, select `User.Read.All` under **Microsoft APIs** > **Microsoft Graph** > **Application Permissions**.
4949
2. Select **Grant admin consent for {tenant}**.
5050
1. Clone this repository `git clone https://github.com/Azure-Samples/ms-identity-javascript-nodejs-console.git`
5151
1. Open the [.env](.env) file and provide the required configuration values.
52-
1. Replace the string `Enter_the_Tenant_Info_Here` with your tenant ID on Azure AD portal.
53-
2. Replace the string `Enter_the_Application_Id_Here` with your app/client ID on Azure AD portal.
54-
3. Replace the string `Enter_the_Client_Secret_Here` with the client secret you created on Azure AD portal.
52+
1. Replace the string `Enter_the_Tenant_Info_Here` with your tenant ID on Microsoft Entra admin center.
53+
2. Replace the string `Enter_the_Application_Id_Here` with your app/client ID on Microsoft Entra admin center.
54+
3. Replace the string `Enter_the_Client_Secret_Here` with the client secret you created on Microsoft Entra admin center.
5555
4. Replace the string `Enter_the_Cloud_Instance_Id_Here` with `https://login.microsoftonline.com/` (see **note** below).
5656
5. Replace the string `Enter_the_Graph_Endpoint_Here`. with `https://graph.microsoft.com/` (see **note** below).
5757

0 commit comments

Comments
 (0)