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/manage-apps/assign-user-or-group-access-portal.md
+9-2Lines changed: 9 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,19 +12,26 @@ ms.topic: how-to
12
12
ms.date: 10/23/2021
13
13
ms.author: ergreenl
14
14
ms.reviewer: davidmu
15
+
ms.custom: contperf-fy22q2, contperf-fy22q3
15
16
16
17
#customer intent: As an admin, I want to manage user assignment for an app in Azure Active Directory using Powershell
17
18
---
18
19
19
20
# Assign users and groups to an application
20
21
21
-
This article shows you how to assign users and groups to an enterprise application in Azure Active Directory (Azure AD) using PowerShell. When you assign a user to an application, the application appears in the user's My Apps portal for easy access. If the application exposes roles, you can also assign a specific role to the user.
22
+
This article shows you how to assign users and groups to an enterprise application in Azure Active Directory (Azure AD) using PowerShell. When you assign a user to an application, the application appears in the user's [My Apps](https://myapps.microsoft.com/) portal for easy access. If the application exposes roles, you can also assign a specific role to the user.
23
+
24
+
When you assign a group to an application, only users in the group will have access. The assignment does not cascade to nested groups.
25
+
26
+
Group-based assignment requires Azure Active Directory Premium P1 or P2 edition. Group-based assignment is supported for Security groups only. Nested group memberships and Microsoft 365 groups are not currently supported. For more licensing requirements for the features discussed in this article, see the [Azure Active Directory pricing page](https://azure.microsoft.com/pricing/details/active-directory).
27
+
28
+
For greater control, certain types of enterprise applications can be configured to require user assignment. See [Manage access to an application](what-is-access-management.md#requiring-user-assignment-for-an-app) for more information on requiring user assignment for an app.
22
29
23
30
## Prerequisites
24
31
25
32
To assign users to an app using PowerShell, you need:
26
33
27
-
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
34
+
- An Azure account with an active subscription. If you don't already have one, you can [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
28
35
- One of the following roles: Global Administrator, Cloud Application Administrator, Application Administrator, or owner of the service principal.
29
36
- If you have not yet installed the AzureAD module (use the command `Install-Module -Name AzureAD`). If you're prompted to install a NuGet module or the new Azure Active Directory V2 PowerShell module, type Y and press ENTER.
30
37
- Azure Active Directory Premium P1 or P2 for group-based assignment. For more licensing requirements for the features discussed in this article, see the [Azure Active Directory pricing page](https://azure.microsoft.com/pricing/details/active-directory).
In this article, you'll learn how to configure F5's BIG-IP Access Policy Manager (APM) and Azure Active Directory (Azure AD) for secure hybrid access to form-based applications.
17
17
18
-
Configuring BIG-IP published applications with Azure AD provides many benefits, including:
18
+
Enabling BIG-IP published services for Azure Active Directory (Azure AD) SSO provides many benefits, including:
19
19
20
-
- Improved Zero Trust governance through Azure AD pre-authentication and authorization
20
+
- Improved Zero Trust governance through Azure AD pre-authentication and [Conditional Access](/conditional-access/overview)
21
21
- Full single sign-on (SSO) between Azure AD and BIG-IP published services
22
-
- Identities and access are managed from a single control plane, the Azure portal
22
+
- Identities and access are managed from a single control plane, the [Azure portal](https://azure.microsoft.com/features/azure-portal/)
23
23
24
24
To learn about all the benefits, see [Integrate F5 BIG-IP with Azure Active Directory](f5-aad-integration.md) and [What is application access and single sign-on with Azure AD?](../active-directory-appssoaccess-whatis.md).
Copy file name to clipboardExpand all lines: articles/active-directory/manage-apps/f5-big-ip-header-advanced.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
@@ -19,12 +19,12 @@ In this article, you’ll learn to implement Secure Hybrid Access (SHA) with sin
19
19
20
20
Configuring BIG-IP published applications with Azure AD provides many benefits, including:
21
21
22
-
- Improved Zero trust governance through Azure AD pre-authentication and authorization
22
+
- Improved Zero trust governance through Azure AD pre-authentication and [Conditional Access](/conditional-access/overview)
23
23
24
24
- Full Single sign-on (SSO) between Azure AD and BIG-IP published
25
25
services.
26
26
27
-
- Manage identities and access from a single control plane, The[Azure portal](https://azure.microsoft.com/features/azure-portal)
27
+
- Manage identities and access from a single control plane, the[Azure portal](https://azure.microsoft.com/features/azure-portal)
28
28
29
29
To learn about all of the benefits, see the article on [F5 BIG-IP and Azure AD integration](./f5-aad-integration.md) and [what is application access and single sign-on with Azure AD](/azure/active-directory/active-directory-appssoaccess-whatis).
Copy file name to clipboardExpand all lines: articles/active-directory/manage-apps/f5-big-ip-headers-easy-button.md
+2-6Lines changed: 2 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,11 +19,11 @@ In this article, you’ll learn to implement Secure Hybrid Access (SHA) with sin
19
19
20
20
Enabling BIG-IP published services for Azure Active Directory (Azure AD) SSO provides many benefits, including:
21
21
22
-
* Improved Zero Trust governance through Azure AD pre-authentication and authorization
22
+
* Improved Zero Trust governance through Azure AD pre-authentication and [Conditional Access](/conditional-access/overview)
23
23
24
24
* Full SSO between Azure AD and BIG-IP published services
25
25
26
-
* Manage Identities and access from a single control plane, [the Azure portal](https://portal.azure.com/)
26
+
* Manage Identities and access from a single control plane, the [Azure portal](https://portal.azure.com/)
27
27
28
28
To learn about all of the benefits, see the article on [F5 BIG-IP and Azure AD integration](./f5-aad-integration.md) and [what is application access and single sign-on with Azure AD](/azure/active-directory/active-directory-appssoaccess-whatis).
29
29
@@ -298,15 +298,11 @@ Our backend application sits on HTTP port 80 but obviously switch to 443 if your
298
298
Enabling SSO allows users to access BIG-IP published services without having to enter credentials. The **Easy Button wizard** supports Kerberos, OAuth Bearer, and HTTP authorization headers for SSO, the latter of which we’ll enable to configure the following.
Copy file name to clipboardExpand all lines: articles/active-directory/manage-apps/f5-big-ip-kerberos-advanced.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,11 +19,9 @@ In this tutorial, you'll learn to implement Secure Hybrid Access (SHA) with sing
19
19
20
20
Integrating a BIG-IP with Azure Active Directory (Azure AD) provides many benefits, including:
21
21
22
-
* Improved Zero Trust governance through Azure AD pre-authentication and authorization.
23
-
22
+
* Improved Zero Trust governance through Azure AD pre-authentication and [Conditional Access](/conditional-access/overview)
24
23
* Full SSO between Azure AD and BIG-IP published services.
25
-
26
-
* Management of identities and access from a single control plane, the [Azure portal](https://portal.azure.com/).
24
+
* Management of identities and access from a single control plane, the [Azure portal](https://azure.microsoft.com/features/azure-portal/)
27
25
28
26
To learn about all of the benefits, see [Integrate F5 BIG-IP with Azure Active Directory](./f5-aad-integration.md) and [What is single sign-on in Azure Active Directory?](/azure/active-directory/active-directory-appssoaccess-whatis).
Copy file name to clipboardExpand all lines: articles/active-directory/manage-apps/f5-big-ip-kerberos-easy-button.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
@@ -19,11 +19,11 @@ In this article, you'll learn to implement Secure Hybrid Access (SHA) with singl
19
19
20
20
Integrating a BIG-IP with Azure Active Directory (Azure AD) provides many benefits, including:
21
21
22
-
* Improved Zero Trust governance through Azure AD pre-authentication and authorization
22
+
* Improved Zero Trust governance through Azure AD pre-authentication and [Conditional Access](/conditional-access/overview)
23
23
24
24
* Full SSO between Azure AD and BIG-IP published services
25
25
26
-
* Manage identities and access from a single control plane, [The Azure portal](https://portal.azure.com/)
26
+
* Manage identities and access from a single control plane, the [Azure portal](https://portal.azure.com/)
27
27
28
28
To learn about all of the benefits, see the article on [F5 BIG-IP and Azure AD integration](./f5-aad-integration.md) and [what is application access and single sign-on with Azure AD](/azure/active-directory/active-directory-appssoaccess-whatis).
# Customer intent: As an IT admin, I need to learn about single sign-on and my applications in Azure Active Directory.
17
17
---
18
18
@@ -52,7 +52,7 @@ Choosing an SSO method depends on how the application is configured for authenti
52
52
- You're testing other aspects of the application
53
53
- An on-premises application doesn't require users to authenticate, but you want them to. With SSO disabled, the user needs to authenticate.
54
54
55
-
If you configured the application for SP-initiated SAML-based SSO and you change the SSO mode to disabled, it won't stop users from signing in to the application outside the MyApps portal. To achieve this, you need to [disable the ability for users to sign in](disable-user-sign-in-portal.md).
55
+
If you configured the application for SP-initiated SAML-based SSO and you change the SSO mode to disabled, it won't stop users from signing in to the application outside the MyApps portal. To achieve this, you need to disable the ability for users to sign in.
Install <ahref="https://www.visualstudio.com/downloads/"target="_blank">Visual Studio 2022</a> with the **ASP.NET and web development**workload.
33
+
Install <ahref="https://www.visualstudio.com/downloads/"target="_blank">Visual Studio 2022</a> with the **ASP.NET and web development**and **Azure development** workloads.
35
34
36
35
If you've installed Visual Studio already, add the workloads in Visual Studio by clicking **Tools** > **Get Tools and Features**.
37
36
@@ -172,7 +171,7 @@ Before creating a database, you need a [logical SQL server](../azure-sql/databas
172
171
173
172
#### Deploy your ASP.NET app
174
173
175
-
1. In the **Publish** tab scroll back up to the top and click **Publish**. Once your ASP.NET app is deployed to Azure. Your default browser is launched with the URL to the deployed app.
174
+
1. In the **Publish** tab, scroll back up to the top and click **Publish**. Once your ASP.NET app is deployed to Azure. Your default browser is launched with the URL to the deployed app.
176
175
177
176
1. Add a few to-do items.
178
177
@@ -182,7 +181,7 @@ Before creating a database, you need a [logical SQL server](../azure-sql/databas
182
181
183
182
## Access the database locally
184
183
185
-
Visual Studio lets you explore and manage your new database in Azure easily in the **SQL Server Object Explorer**. The new database already opened its firewall to the App Service app that you created, but to access it from your local computer (such as from Visual Studio), you must open a firewall for your local machine's public IP address. If your internet service provider changes your public IP address, you need to reconfigure the firewall to access the Azure database again.
184
+
Visual Studio lets you explore and manage your new database in Azure easily in the **SQL Server Object Explorer**. The new database already opened its firewall to the App Service app that you created. But to access it from your local computer (such as from Visual Studio), you must open a firewall for your local machine's public IP address. If your internet service provider changes your public IP address, you need to reconfigure the firewall to access the Azure database again.
186
185
187
186
#### Create a database connection
188
187
@@ -350,11 +349,9 @@ Each action starts with a `Trace.WriteLine()` method. This code is added to show
350
349
351
350
#### Enable log streaming
352
351
353
-
1. From the **View** menu, select **Cloud Explorer**.
352
+
1. In the publish page, scroll down to the **Hosting** section.
354
353
355
-
1. In **Cloud Explorer**, expand the Azure subscription that has your app and expand **App Service**.
356
-
357
-
1. Right-click your Azure app and select **View Streaming Logs**.
354
+
1. At the right-hand corner, click **...** > **View Streaming Logs**.
@@ -366,16 +363,14 @@ Each action starts with a `Trace.WriteLine()` method. This code is added to show
366
363
367
364
#### Change trace levels
368
365
369
-
1. To change the trace levels to output other trace messages, go back to **Cloud Explorer**.
366
+
1. To change the trace levels to output other trace messages, go back to the publish page.
370
367
371
-
1. Right-click your app again and select **Open in Portal**.
368
+
1. In the **Hosting** section, click **...** > **Open in Azure portal**.
372
369
373
370
1. In the portal management page for your app, from the left menu, select **App Service logs**.
374
371
375
372
1. Under **Application Logging (File System)**, select **Verbose** in **Level**. Click **Save**.
376
373
377
-

378
-
379
374
> [!TIP]
380
375
> You can experiment with different trace levels to see what types of messages are displayed for each level. For example, the **Information** level includes all logs created by `Trace.TraceInformation()`, `Trace.TraceWarning()`, and `Trace.TraceError()`, but not logs created by `Trace.WriteLine()`.
381
376
@@ -394,22 +389,6 @@ To stop the log-streaming service, click the **Stop monitoring** button in the *
Go to the [Azure portal](https://portal.azure.com) to manage the web app. Search for and select **App Services**.
400
-
401
-

402
-
403
-
Select the name of your Azure app.
404
-
405
-

406
-
407
-
You have landed in your app's page.
408
-
409
-
By default, the portal shows the **Overview** page. This page gives you a view of how your app is doing. Here, you can also perform basic management tasks like browse, stop, start, restart, and delete. The tabs on the left side of the page show the different configuration pages you can open.
410
-
411
-

412
-
413
392
[!INCLUDE [Clean up section](../../includes/clean-up-section-portal-web-app.md)]
414
393
415
394
## Next steps
@@ -423,12 +402,11 @@ In this tutorial, you learned how to:
423
402
> * Deploy the app to Azure
424
403
> * Update the data model and redeploy the app
425
404
> * Stream logs from Azure to your terminal
426
-
> * Manage the app in the Azure portal
427
405
428
406
Advance to the next tutorial to learn how to easily improve the security of your connection Azure SQL Database.
429
407
430
408
> [!div class="nextstepaction"]
431
-
> [Access SQL Database securely using managed identities for Azure resources](tutorial-connect-msi-sql-database.md)
409
+
> [Tutorial: Connect to SQL Database from App Service without secrets using a managed identity](tutorial-connect-msi-sql-database.md)
Copy file name to clipboardExpand all lines: articles/app-service/environment/overview.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,7 +62,7 @@ The multi-tenant version of Azure App Service contains numerous features to enab
62
62
63
63
## Feature differences
64
64
65
-
Compared to earlier versions of the App Service Environment, there are some differences with App Service Environment v3. With App Service Environment v3:
65
+
Compared to earlier versions of the App Service Environment, there are some differences with App Service Environment v3:
66
66
67
67
- There are no networking dependencies in the customer virtual network. You can secure all inbound and outbound as desired. Outbound traffic can be routed also as desired.
68
68
- You can deploy it enabled for zone redundancy. Zone redundancy can only be set during creation and only in regions where all App Service Environment v3 dependencies are zone redundant.
0 commit comments