You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AppCreationScripts/AppCreationScripts.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@
11
11
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process -Force
12
12
```
13
13
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.
15
15
16
16
```PowerShell
17
17
cd .\AppCreationScripts\
@@ -35,23 +35,23 @@
35
35
36
36
### Presentation of the scripts
37
37
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.
39
39
40
40
These scripts are:
41
41
42
42
-`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),
44
44
- 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:
46
46
- the identifier of the application
47
47
- 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).
49
49
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`).
51
51
52
52
### Usage pattern for tests and DevOps scenarios
53
53
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.
55
55
56
56
## How to use the app creation scripts?
57
57
@@ -116,8 +116,8 @@ Note that the script will choose the tenant in which to create the applications,
116
116
117
117
if you want to create the apps in a particular tenant, you can use the following option:
118
118
119
-
- Open the [Azure portal](https://portal.azure.com)
120
-
- Select the Azure Active directory you are interested in (in the combo-box below your name on the top right of the browser window)
119
+
- Open the [Microsoft Entra admin center](https://entra.microsoft.com)
120
+
- Select the Microsoft Entra ID you are interested in (in the combo-box below your name on the top right of the browser window)
121
121
- Find the "Active Directory" object in this tenant
122
122
- Go to **Properties** and copy the content of the **Directory Id** property
@@ -41,7 +41,7 @@ Write your app like this once, and the same implementation will support 4x2=8 sc
41
41
<th>Microsoft Entra ID</th>
42
42
<th>Microsoft Entra External ID</th>
43
43
<th>Microsoft Entra External ID with Custom Domain</th>
44
-
<th>Azure AD B2C</th>
44
+
<th>Azure Active Directory B2C</th>
45
45
</tr>
46
46
47
47
<tr>
@@ -65,7 +65,7 @@ Coming soon.
65
65
<td>
66
66
67
67
Following only the step 1 and 2 (including 2.1 and 2.2) of this
68
-
[Configure authentication in a sample Python web app by using Azure AD B2C](https://learn.microsoft.com/azure/active-directory-b2c/configure-authentication-sample-python-web-app?tabs=linux)
68
+
[Configure authentication in a sample Python web app by using Azure Active Directory B2C](https://learn.microsoft.com/azure/active-directory-b2c/configure-authentication-sample-python-web-app?tabs=linux)
69
69
70
70
</td>
71
71
</tr>
@@ -92,7 +92,7 @@ as `.env` and then modify `.env` with your app's settings.
92
92
</td>
93
93
<td>
94
94
95
-
Copy this [Azure AD B2C template](.env.sample.b2c)
95
+
Copy this [Azure Active Directory B2C template](.env.sample.b2c)
96
96
as `.env` and then modify `.env` with your app's settings.
0 commit comments