accessPackageResourceRoleScope resource type
Namespace: microsoft.graph
In Microsoft Entra entitlement management, an access package resource role scope is a reference to both a scope within a resource, and a role in that resource for that scope. An access package will have access package resource role scopes for the resources in its catalog which are relevant to that access package. When a subject receives an access package assignment, the subject will be provisioned with the role in that scope of each access package resource role scope.
Methods
Method | Return Type | Description |
---|---|---|
List accessPackageResourceRoleScopes | accessPackageResourceRoleScope collection | Retrieve a list of accessPackageResourceRoleScope objects for an access package. |
Create accessPackageResourceRoleScope | accessPackageResourceRoleScope | Create a new accessPackageResourceRoleScope object for an access package. |
Delete accessPackageResourceRoleScope | None | Delete an accessPackageResourceRoleScope object from an access package. |
Properties
Property | Type | Description |
---|---|---|
createdDateTime | DateTimeOffset | The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z |
id | String | Read-only. |
Relationships
Relationship | Type | Description |
---|---|---|
role | accessPackageResourceRole | Read-only. Nullable. |
scope | accessPackageResourceScope | Read-only. Nullable. |
JSON representation
The following is a JSON representation of the resource.
{
"createdDateTime":"String (timestamp)",
"id":"String (identifier)",
"modifiedDateTime":"String (timestamp)",
"accessPackageResourceRole":{
"id":"String (identifier)",
"displayName":"String",
"originSystem":"String",
"originId":"String"
},
"accessPackageResourceScope":{
"id":"String (identifier)",
"displayName":"String",
"description":"String",
"originId":"String (identifier)",
"originSystem":"String"
}
}
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for