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: articles/active-directory/conditional-access/concept-conditional-access-cloud-apps.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.subservice: conditional-access
8
8
ms.custom: has-azure-ad-ps-ref
9
9
ms.topic: conceptual
10
10
11
-
ms.date: 08/25/2023
11
+
ms.date: 08/31/2023
12
12
13
13
ms.author: joflore
14
14
author: MicrosoftGuyJFlo
@@ -185,7 +185,7 @@ User actions are tasks that can be performed by a user. Currently, Conditional A
185
185
186
186
## Traffic forwarding profiles
187
187
188
-
Traffic forwarding profiles in Global Secure Access enable administrators to define and control how traffic is routed through Microsoft Entra Internet Access and Microsoft Entra Private Access. Traffic forwarding profiles can be assigned to devices and remote networks. For an example of how to configure these traffic profiles in Conditional Access policy, see the article [How to require a compliant network check](../../global-secure-access/how-to-compliant-network.md).
188
+
Traffic forwarding profiles in Global Secure Access enable administrators to define and control how traffic is routed through Microsoft Entra Internet Access and Microsoft Entra Private Access. Traffic forwarding profiles can be assigned to devices and remote networks. For an example of how to apply a Conditional Access policy to these traffic profiles, see the article [How to apply Conditional Access policies to the Microsoft 365 traffic profile](../../global-secure-access/how-to-target-resource-microsoft-365-profile.md).
189
189
190
190
For more information about these profiles, see the article [Global Secure Access traffic forwarding profiles](../../global-secure-access/concept-traffic-forwarding.md).
Copy file name to clipboardExpand all lines: articles/active-directory/develop/tutorial-v2-angular-auth-code.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ In this tutorial:
23
23
24
24
> [!div class="checklist"]
25
25
>
26
-
> - Register the application in the Azure portal
26
+
> - Register the application in the Microsoft Entra admin center
27
27
> - Create an Angular project with `npm`
28
28
> - Add code to support user sign-in and sign-out
29
29
> - Add code to call Microsoft Graph API
@@ -71,10 +71,10 @@ To continue with the tutorial and build the application yourself, move on to the
71
71
72
72
To complete registration, provide the application a name, specify the supported account types, and add a redirect URI. Once registered, the application **Overview** pane displays the identifiers needed in the application source code.
73
73
74
-
1. Sign in to the [Azure portal](https://portal.azure.com).
75
-
1. If access to multiple tenants is available, use the **Directories + subscriptions** filter :::image type="icon" source="media/common/portal-directory-subscription-filter.png" border="false"::: in the top menu to switch to the tenant in which to register the application.
76
-
1.Search for and select**Azure Active Directory**.
77
-
1.Under**Manage**, select **App registrations > New registration**.
74
+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Application Developer](../roles/permissions-reference.md#application-developer).
75
+
1. If access to multiple tenants is available, use the **Directories + subscriptions** filter :::image type="icon" source="media/common/portal-directory-subscription-filter.png" border="false"::: in the top menu to switch to the tenant in which you want to register the application.
76
+
1.Browse to **Identity** >**Applications** > **App registrations**.
77
+
1.Select**New registration**.
78
78
1. Enter a **Name** for the application, such as _Angular-SPA-auth-code_.
79
79
1. For **Supported account types**, select **Accounts in this organizational directory only**. For information on different account types, select the **Help me choose** option.
80
80
1. Under **Redirect URI (optional)**, use the drop-down menu to select **Single-page-application (SPA)** and enter `http://localhost:4200` into the text box.
@@ -155,7 +155,7 @@ To complete registration, provide the application a name, specify the supported
155
155
exportclassAppModule {}
156
156
```
157
157
158
-
1. Replace the following values with the values obtained from the Azure portal. For more information about available configurable options, see [Initialize client applications](msal-js-initializing-client-applications.md).
158
+
1. Replace the following values with the values obtained from the Microsoft Entra admin center. For more information about available configurable options, see [Initialize client applications](msal-js-initializing-client-applications.md).
159
159
160
160
-`clientId` - The identifier of the application, also referred to as the client. Replace `Enter_the_Application_Id_Here` with the **Application (client) ID** value that was recorded earlier from the overview page of the registered application.
161
161
-`authority` - This is composed of two parts:
@@ -994,7 +994,7 @@ MSAL Angular provides an `Interceptor` class that automatically acquires tokens
994
994
995
995
## Add scopes and delegated permissions
996
996
997
-
The Microsoft Graph API requires the _User.Read_ scope to read a user's profile. The _User.Read_ scope is added automatically to every app registration you create in the Azure portal. Other APIs for Microsoft Graph, and custom APIs for your back-end server, might require other scopes. For example, the Microsoft Graph API requires the _Mail.Read_ scope in order to list the user's email.
997
+
The Microsoft Graph API requires the _User.Read_ scope to read a user's profile. The _User.Read_ scope is added automatically to every app registration. Other APIs for Microsoft Graph, and custom APIs for your back-end server, might require other scopes. For example, the Microsoft Graph API requires the _Mail.Read_ scope in order to list the user's email.
998
998
999
999
As you add scopes, your users might be prompted to provide extra consent for the added scopes.
Copy file name to clipboardExpand all lines: articles/active-directory/develop/tutorial-v2-aspnet-daemon-web-app.md
+12-18Lines changed: 12 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,13 +28,13 @@ In this tutorial:
28
28
> * Get an access token to call the Microsoft Graph API
29
29
> * Call the Microsoft Graph API.
30
30
31
-
If you don’t have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
31
+
If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
32
32
33
33
## Prerequisites
34
34
35
35
-[Visual Studio 2017 or 2019](https://visualstudio.microsoft.com/downloads/).
36
36
- An Azure AD tenant. For more information, see [How to get an Azure AD tenant](quickstart-create-new-tenant.md).
37
-
- One or more user accounts in your Azure AD tenant. This sample won't work with a Microsoft account. If you signed in to the [Azure portal](https://portal.azure.com) with a Microsoft account and have never created a user account in your directory, do that now.
37
+
- One or more user accounts in your tenant. This sample won't work with a Microsoft account. If you signed in with a Microsoft account and have never created a user account in your directory, do that now.
38
38
39
39
## Scenario
40
40
@@ -62,7 +62,7 @@ Or [download the sample in a zip file](https://github.com/Azure-Samples/ms-ident
62
62
63
63
This sample has one project. To register the application with your Azure AD tenant, you can either:
64
64
65
-
- Follow the steps in [Register the sample with your Azure Active Directory tenant](#register-the-client-app-dotnet-web-daemon-v2) and [Configure the sample to use your Azure AD tenant](#choose-the-azure-ad-tenant).
65
+
- Follow the steps in [Choose the tenant](#choose-the-tenant) and [Configure the sample to use your tenant](#configure-the-sample-to-use-your-tenant).
66
66
- Use PowerShell scripts that:
67
67
-*Automatically* create the Azure AD applications and related objects (passwords, permissions, dependencies) for you.
68
68
- Modify the Visual Studio projects' configuration files.
@@ -88,18 +88,14 @@ If you want to use the automation:
88
88
89
89
If you don't want to use the automation, use the steps in the following sections.
1. Sign in to the <ahref="https://portal.azure.com/"target="_blank">Azure portal</a>.
96
-
1. If you have access to multiple tenants, use the **Directories + subscriptions** filter :::image type="icon" source="./media/common/portal-directory-subscription-filter.png" border="false"::: in the top menu to switch to the tenant in which you want to register the application.
97
-
98
-
99
-
### Register the client app (dotnet-web-daemon-v2)
100
-
101
-
1. Search for and select **Azure Active Directory**.
102
-
1. Under **Manage**, select **App registrations** > **New registration**.
95
+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Application Developer](../roles/permissions-reference.md#application-developer).
96
+
1. If access to multiple tenants is available, use the **Directories + subscriptions** filter :::image type="icon" source="media/common/portal-directory-subscription-filter.png" border="false"::: in the top menu to switch to the tenant in which you want to register the application.
97
+
1. Browse to **Identity** > **Applications** > **App registrations**.
98
+
1. Select **New registration**.
103
99
1. Enter a **Name** for your application, for example `dotnet-web-daemon-v2`. Users of your app might see this name, and you can change it later.
104
100
1. In the **Supported account types** section, select **Accounts in any organizational directory**.
105
101
1. In the **Redirect URI (optional)** section, select **Web** in the combo box and enter `https://localhost:44316/` and `https://localhost:44316/Account/GrantPermissions` as Redirect URIs.
@@ -121,7 +117,7 @@ If you don't want to use the automation, use the steps in the following sections
121
117
1. In the **Application permissions** section, ensure that the right permissions are selected: **User.Read.All**.
122
118
1. Select **Add permissions**.
123
119
124
-
## Configure the sample to use your Azure AD tenant
120
+
## Configure the sample to use your tenant
125
121
126
122
In the following steps, **ClientID** is the same as "application ID" or **AppId**.
127
123
@@ -132,8 +128,8 @@ Open the solution in Visual Studio to configure the projects.
132
128
If you used the setup scripts, the following changes will have been applied for you.
133
129
134
130
1. Open the **UserSync\Web.Config** file.
135
-
1. Find the app key **ida:ClientId**. Replace the existing value with the application ID of the **dotnet-web-daemon-v2** application copied from the Azure portal.
136
-
1. Find the app key **ida:ClientSecret**. Replace the existing value with the key that you saved during the creation of the **dotnet-web-daemon-v2** app in the Azure portal.
131
+
1. Find the app key **ida:ClientId**. Replace the existing value with the application ID of the **dotnet-web-daemon-v2** application that was previously recorded.
132
+
1. Find the app key **ida:ClientSecret**. Replace the existing value with the key that you saved during the creation of the **dotnet-web-daemon-v2** app.
137
133
138
134
## Run the sample
139
135
@@ -223,9 +219,7 @@ Visual Studio will publish the project and automatically open a browser to the p
223
219
224
220
### Update the Azure AD tenant application registration for dotnet-web-daemon-v2
225
221
226
-
1. Go back to the <ahref="https://portal.azure.com/"target="_blank">Azure portal</a>.
227
-
1. In the left pane, select the **Azure Active Directory** service, and then select **App registrations**.
228
-
1. Select the **dotnet-web-daemon-v2** application.
222
+
1. Go back to the Microsoft Entra admin center, and then select the **dotnet-web-daemon-v2** application in **App registrations**.
229
223
1. On the **Authentication** page for your application, update the **Front-channel logout URL** fields with the address of your service. For example, use `https://dotnet-web-daemon-v2-contoso.azurewebsites.net/Account/EndSession`.
230
224
1. From the **Branding** menu, update the **Home page URL** to the address of your service. For example, use `https://dotnet-web-daemon-v2-contoso.azurewebsites.net`.
1. Sign in to the <ahref="https://portal.azure.com/"target="_blank">Azure portal</a>.
71
-
1. If you have access to multiple tenants, use the **Directories + subscriptions** filter :::image type="icon" source="./media/common/portal-directory-subscription-filter.png" border="false"::: in the top menu to switch to the tenant in which you want to register the application.
72
-
1.Search for and select**Azure Active Directory**.
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Application Developer](../roles/permissions-reference.md#application-developer).
71
+
1. If access to multiple tenants is available, use the **Directories + subscriptions** filter :::image type="icon" source="media/common/portal-directory-subscription-filter.png" border="false"::: in the top menu to switch to the tenant in which you want to register the application.
72
+
1.Browse to **Identity** >**Applications** > **App registrations**.
73
+
1.Select**New registration**.
74
74
1. Enter a **Name** for your application. Users of your app might see this name, and you can change it later.
75
75
1. Select **Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)** under **Supported account types**.
You can also use Git Submodule, or check out the latest release to use as a framework in your application.
127
127
128
-
## Add your app registration
128
+
## Add the app registration
129
129
130
130
Next, we add your app registration to your code.
131
131
@@ -138,7 +138,7 @@ import MSAL
138
138
Next, add the following code to _ViewController.swift_ before to `viewDidLoad()`:
139
139
140
140
```swift
141
-
// Update the below to your client ID you received in the portal. The below is for running the demo only
141
+
// Update the below to your client ID. The below is for running the demo only
142
142
let kClientID ="Your_Application_Id_Here"
143
143
let kGraphEndpoint ="https://graph.microsoft.com/"// the Microsoft Graph endpoint
144
144
let kAuthority ="https://login.microsoftonline.com/common"// this authority allows a personal Microsoft account and a work or school account in any organization's Azure AD tenant to sign in
@@ -151,7 +151,7 @@ var webViewParameters : MSALWebviewParameters?
151
151
var currentAccount: MSALAccount?
152
152
```
153
153
154
-
The only value you modify is the value assigned to `kClientID` to be your [Application ID](./developer-glossary.md#application-client-id). This value is part of the MSAL Configuration data that you saved during the step at the beginning of this tutorial to register the application in the Azure portal.
154
+
The only value you modify is the value assigned to `kClientID` to be your [Application ID](./developer-glossary.md#application-client-id). This value is part of the MSAL Configuration data that you saved during the step at the beginning of this tutorial to register the application.
155
155
156
156
## Configure Xcode project settings
157
157
@@ -163,7 +163,7 @@ Add a new keychain group to your project **Signing & Capabilities**. The keychai
163
163
164
164
In this step, you'll register `CFBundleURLSchemes` so that the user can be redirected back to the app after sign in. By the way, `LSApplicationQueriesSchemes` also allows your app to make use of Microsoft Authenticator.
165
165
166
-
In Xcode, open _Info.plist_ as a source code file, and add the following inside of the `<dict>` section. Replace `[BUNDLE_ID]` with the value you used in the Azure portal. If you downloaded the code, the bundle identifier is `com.microsoft.identitysample.MSALiOS`. If you're creating your own project, select your project in Xcode and open the **General** tab. The bundle identifier appears in the **Identity** section.
166
+
In Xcode, open _Info.plist_ as a source code file, and add the following inside of the `<dict>` section. Replace `[BUNDLE_ID]` with the value you previously used. If you downloaded the code, the bundle identifier is `com.microsoft.identitysample.MSALiOS`. If you're creating your own project, select your project in Xcode and open the **General** tab. The bundle identifier appears in the **Identity** section.
167
167
168
168
```xml
169
169
<key>CFBundleURLTypes</key>
@@ -846,7 +846,7 @@ This app is built for a single account scenario. MSAL also supports multi-accoun
846
846
847
847
Build and deploy the app to a test device or simulator. You should be able to sign in and get tokens for Azure AD or personal Microsoft accounts.
848
848
849
-
The first time a user signs into your app, they'll be prompted by Microsoft identity to consent to the permissions requested. While most users are capable of consenting, some Azure AD tenants have disabled user consent, which requires admins to consent on behalf of all users. To support this scenario, register your app's scopes in the Azure portal.
849
+
The first time a user signs into your app, they'll be prompted by Microsoft identity to consent to the permissions requested. While most users are capable of consenting, some Azure AD tenants have disabled user consent, which requires admins to consent on behalf of all users. To support this scenario, register your app's scopes.
850
850
851
851
After you sign in, the app will display the data returned from the Microsoft Graph `/me` endpoint.
0 commit comments