Skip to content

Commit

Permalink
Merge pull request MicrosoftDocs#18753 from curtand/class0804
Browse files Browse the repository at this point in the history
added Important note re: classic portal
  • Loading branch information
PRMerger6 authored Aug 7, 2017
2 parents 05f98fb + 863330e commit c6d730d
Showing 1 changed file with 6 additions and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -13,13 +13,18 @@ ms.workload: identity
ms.tgt_pltfrm: na
ms.devlang: na
ms.topic: article
ms.date: 05/08/2017
ms.date: 08/04/2017
ms.author: curtand
ms.reviewer: piotrci
ms.custom: it-pro;oldportal

---
# Using a group to manage access to SaaS applications
Using Azure Active Directory (Azure AD) with an Azure AD Premium or Azure AD Basic license, you can use groups to assign access to a SaaS application that's integrated with Azure AD. For example, if you want to assign access for the marketing department to use five different SaaS applications, you can create a group that contains the users in the marketing department, and then assign that group to these five SaaS applications that are needed by the marketing department. This way you can save time by managing the membership of the marketing department in one place. Users then are assigned to the application when they are added as members of the marketing group, and have their assignments removed from the application when they are removed from the marketing group.

> [!IMPORTANT]
> Microsoft recommends that you manage Azure AD using the [Azure AD admin center](https://aad.portal.azure.com) in the Azure portal instead of using the Azure classic portal referenced in this article.
This capability can be used with hundreds of applications that you can add from within the Azure AD Application Gallery.

**To assign access for a group to a SaaS application**
Expand Down

0 comments on commit c6d730d

Please sign in to comment.