Skip to content

Commit 3891b4a

Browse files
wwlpublishwwlpublish
authored
changed files by pdets auto publish service, publishid[c05f1fe6-5679-46e9-bba7-6a3acb9ce002] and do [publish].
1 parent 3f34ada commit 3891b4a

File tree

4 files changed

+89
-87
lines changed

4 files changed

+89
-87
lines changed

‎learn-pr/wwl-sci/plan-implement-entitlement-management/includes/2-define-access-packages.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -11,33 +11,33 @@ This video provides an overview of entitlement management and its value:
1111

1212
**Watch this video to learn more about Microsoft Entra entitlement management**
1313

14-
> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4MFIb]
14+
> [!VIDEO https://learn-video.azurefd.net/vod/player?id=7688733a-4672-4c14-a811-98e324ceeb0b]
1515
1616
## What can I do with entitlement management?
1717

1818
Capabilities of entitlement management include:
1919

20-
| **Entitlement management capability** | **Description and value** |
21-
| --------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
22-
| Delegate to non-administrators the ability to create access packages. | These access packages contain resources that users can request, and the delegated access package managers can define policies with rules for which users can request, who must approve their access, and when access expires. |
23-
| Select connected organizations whose users can request access. | When a user who isn't yet in your directory requests access and is approved, they're automatically invited into your directory and assigned access. When their access expires, if they have no other access package assignments, their B2B account in your directory can be automatically removed. |
20+
| **Entitlement management capability** | **Description and value** |
21+
| ---------------------------------------- | ---------------------------------------- |
22+
| Delegate to non-administrators the ability to create access packages. | These access packages contain resources that users can request, and the delegated access package managers can define policies with rules for which users can request, who must approve their access, and when access expires. |
23+
| Select connected organizations whose users can request access. | When a user who isn't yet in your directory requests access and is approved, they're automatically invited into your directory and assigned access. When their access expires, if they have no other access package assignments, their B2B account in your directory can be automatically removed. |
2424

2525
## Summary of terminology
2626

2727
Before exploring entitlement management and its documentation in depth, you should know the terms below. Feel free to reference back to this list at any time during this course.
2828

29-
| **Term** | **Description** |
30-
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
31-
| access package | A bundle of resources that a team or project needs and is governed with policies. An access package is always contained in a catalog. You would create a new access package for a scenario in which users need to request access. |
32-
| access request | A request to access the resources in an access package. A request typically goes through an approval workflow. If approved, the requesting user receives an access package assignment. |
33-
| assignment | An assignment of an access package to a user ensures the user has all the resource roles of that access package. Access package assignments typically have a time limit before they expire. |
34-
| catalog | A container of related resources and access packages. Catalogs are used for delegation so non-administrators can create their own access packages. Catalog owners can add resources they own to a catalog. |
35-
| catalog creator | A collection of users who are authorized to create new catalogs. When a non-administrator user who is authorized to be a catalog creator creates a new catalog, they automatically become the owner of that catalog. |
36-
| connected organization | An external Microsoft Entra directory or domain that you have a relationship with. The users from a connected organization can be specified in a policy as being allowed to request access. |
29+
| **Term** | **Description** |
30+
| ---------------------- | ---------------------------------------- |
31+
| access package | A bundle of resources that a team or project needs and is governed with policies. An access package is always contained in a catalog. You would create a new access package for a scenario in which users need to request access. |
32+
| access request | A request to access the resources in an access package. A request typically goes through an approval workflow. If approved, the requesting user receives an access package assignment. |
33+
| assignment | An assignment of an access package to a user ensures the user has all the resource roles of that access package. Access package assignments typically have a time limit before they expire. |
34+
| catalog | A container of related resources and access packages. Catalogs are used for delegation so non-administrators can create their own access packages. Catalog owners can add resources they own to a catalog. |
35+
| catalog creator | A collection of users who are authorized to create new catalogs. When a non-administrator user who is authorized to be a catalog creator creates a new catalog, they automatically become the owner of that catalog. |
36+
| connected organization | An external Microsoft Entra directory or domain that you have a relationship with. The users from a connected organization can be specified in a policy as being allowed to request access. |
3737
| policy | A set of rules that defines the access lifecycle, such as how users get access, who can approve, and how long users have access through an assignment. A policy is linked to an access package. For example, an access package could have two policies: one for employees to request access and a second for external users to request access. |
38-
| resource | An asset, such as an Office group, a security group, an application, or a SharePoint Online site, with a role that a user can be granted permissions to. |
39-
| resource directory | A directory that has one or more resources to share. |
40-
| resource role | A collection of permissions associated with and defined by a resource. A group has two roles: member and owner. SharePoint sites typically have three roles but can have additional custom roles. Applications can have custom roles. |
38+
| resource | An asset, such as an Office group, a security group, an application, or a SharePoint Online site, with a role that a user can be granted permissions to. |
39+
| resource directory | A directory that has one or more resources to share. |
40+
| resource role | A collection of permissions associated with and defined by a resource. A group has two roles: member and owner. SharePoint sites typically have three roles but can have additional custom roles. Applications can have custom roles. |
4141

4242
## What are access packages and what resources can I manage with them?
4343

0 commit comments

Comments
 (0)