Skip to content

Commit 46d696f

Browse files
Microsoft Graph DevX ToolingMicrosoft Graph DevX Tooling
authored andcommitted
Update clean metadata file with 75050 [skip ci]
1 parent c4c4f87 commit 46d696f

1 file changed

Lines changed: 10 additions & 10 deletions

File tree

openapi/v1.0/openapi.yaml

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -90889,8 +90889,8 @@ paths:
9088990889
post:
9089090890
tags:
9089190891
- groups.group
90892-
summary: 'Tutorial: Use the Privileged Identity Management (PIM) API to assign Azure AD roles'
90893-
description: 'In this tutorial, a fictitious company called Contoso Limited wishes to have its IT Helpdesk manage the lifecycle of employees’ access. The company has identified the Azure AD User Administrator role as the appropriate privileged role required by IT Helpdesk, and will use the PIM API to assign the role. You''ll create a role-assignable security group for IT Helpdesk and using the PIM API, assign the security group eligibility to the User Administrator role. By assigning the eligible role to a security group, Contoso has a more efficient way to manage administrator access to resources such as Azure AD roles. For example: Assigning eligibility instead of a persistently active User Administrator privilege allows the company to enforce **just-in-time access**, which grants temporary permissions to carry out the privileged tasks. After defining the role eligibility, the eligible group member then activates their assignment for a temporary period. All records of role activations will be auditable by the company.'
90892+
summary: 'Tutorial: Use the access reviews API to review access to your security groups'
90893+
description: 'Suppose you use Azure AD security groups to assign identities (also called *principals*) access to resources in your organization. Periodically, you need to attest that all members of the security group need their membership and by extension, their access to the resources assigned to the security group. This tutorial guides you to use the access review API to review access to a security group in your Azure AD tenant. You can use Graph Explorer or Postman to try out and test your access reviews API calls before you automate them into a script or an app. This test environment saves you time by helping you properly define and validate your queries without repeatedly recompiling your application.'
9089490894
operationId: groups.group.CreateGroup
9089590895
requestBody:
9089690896
description: New entity
@@ -91073,8 +91073,8 @@ paths:
9107391073
delete:
9107491074
tags:
9107591075
- groups.group
91076-
summary: 'Tutorial: Use the Privileged Identity Management (PIM) API to assign Azure AD roles'
91077-
description: 'In this tutorial, a fictitious company called Contoso Limited wishes to have its IT Helpdesk manage the lifecycle of employees’ access. The company has identified the Azure AD User Administrator role as the appropriate privileged role required by IT Helpdesk, and will use the PIM API to assign the role. You''ll create a role-assignable security group for IT Helpdesk and using the PIM API, assign the security group eligibility to the User Administrator role. By assigning the eligible role to a security group, Contoso has a more efficient way to manage administrator access to resources such as Azure AD roles. For example: Assigning eligibility instead of a persistently active User Administrator privilege allows the company to enforce **just-in-time access**, which grants temporary permissions to carry out the privileged tasks. After defining the role eligibility, the eligible group member then activates their assignment for a temporary period. All records of role activations will be auditable by the company.'
91076+
summary: 'Tutorial: Use the access reviews API to review access to your security groups'
91077+
description: 'Suppose you use Azure AD security groups to assign identities (also called *principals*) access to resources in your organization. Periodically, you need to attest that all members of the security group need their membership and by extension, their access to the resources assigned to the security group. This tutorial guides you to use the access review API to review access to a security group in your Azure AD tenant. You can use Graph Explorer or Postman to try out and test your access reviews API calls before you automate them into a script or an app. This test environment saves you time by helping you properly define and validate your queries without repeatedly recompiling your application.'
9107891078
operationId: groups.group.DeleteGroup
9107991079
parameters:
9108091080
- name: If-Match
@@ -452092,8 +452092,8 @@ paths:
452092452092
post:
452093452093
tags:
452094452094
- users.user
452095-
summary: 'Tutorial: Use the Privileged Identity Management (PIM) API to assign Azure AD roles'
452096-
description: 'In this tutorial, a fictitious company called Contoso Limited wishes to have its IT Helpdesk manage the lifecycle of employees’ access. The company has identified the Azure AD User Administrator role as the appropriate privileged role required by IT Helpdesk, and will use the PIM API to assign the role. You''ll create a role-assignable security group for IT Helpdesk and using the PIM API, assign the security group eligibility to the User Administrator role. By assigning the eligible role to a security group, Contoso has a more efficient way to manage administrator access to resources such as Azure AD roles. For example: Assigning eligibility instead of a persistently active User Administrator privilege allows the company to enforce **just-in-time access**, which grants temporary permissions to carry out the privileged tasks. After defining the role eligibility, the eligible group member then activates their assignment for a temporary period. All records of role activations will be auditable by the company.'
452095+
summary: 'Tutorial: Use the access reviews API to review access to your security groups'
452096+
description: 'Suppose you use Azure AD security groups to assign identities (also called *principals*) access to resources in your organization. Periodically, you need to attest that all members of the security group need their membership and by extension, their access to the resources assigned to the security group. This tutorial guides you to use the access review API to review access to a security group in your Azure AD tenant. You can use Graph Explorer or Postman to try out and test your access reviews API calls before you automate them into a script or an app. This test environment saves you time by helping you properly define and validate your queries without repeatedly recompiling your application.'
452097452097
operationId: users.user.CreateUser
452098452098
requestBody:
452099452099
description: New entity
@@ -452346,8 +452346,8 @@ paths:
452346452346
delete:
452347452347
tags:
452348452348
- users.user
452349-
summary: 'Tutorial: Use the Privileged Identity Management (PIM) API to assign Azure AD roles'
452350-
description: 'In this tutorial, a fictitious company called Contoso Limited wishes to have its IT Helpdesk manage the lifecycle of employees’ access. The company has identified the Azure AD User Administrator role as the appropriate privileged role required by IT Helpdesk, and will use the PIM API to assign the role. You''ll create a role-assignable security group for IT Helpdesk and using the PIM API, assign the security group eligibility to the User Administrator role. By assigning the eligible role to a security group, Contoso has a more efficient way to manage administrator access to resources such as Azure AD roles. For example: Assigning eligibility instead of a persistently active User Administrator privilege allows the company to enforce **just-in-time access**, which grants temporary permissions to carry out the privileged tasks. After defining the role eligibility, the eligible group member then activates their assignment for a temporary period. All records of role activations will be auditable by the company.'
452349+
summary: 'Tutorial: Use the access reviews API to review access to your security groups'
452350+
description: 'Suppose you use Azure AD security groups to assign identities (also called *principals*) access to resources in your organization. Periodically, you need to attest that all members of the security group need their membership and by extension, their access to the resources assigned to the security group. This tutorial guides you to use the access review API to review access to a security group in your Azure AD tenant. You can use Graph Explorer or Postman to try out and test your access reviews API calls before you automate them into a script or an app. This test environment saves you time by helping you properly define and validate your queries without repeatedly recompiling your application.'
452351452351
operationId: users.user.DeleteUser
452352452352
parameters:
452353452353
- name: If-Match
@@ -605189,11 +605189,11 @@ components:
605189605189
properties:
605190605190
key:
605191605191
type: string
605192-
description: Key.
605192+
description: 'Contains the name of the field that a value is associated with. When a sign in or domain hint is included in the sign-in request, corresponding fields are included as key-value pairs. Possible keys: Login hint present, Domain hint present.'
605193605193
nullable: true
605194605194
value:
605195605195
type: string
605196-
description: Value.
605196+
description: Contains the corresponding value for the specified key. The value is true if a sign in hint was included in the sign-in request; otherwise false. The value is true if a domain hint was included in the sign-in request; otherwise false.
605197605197
nullable: true
605198605198
microsoft.graph.modifiedProperty:
605199605199
title: modifiedProperty

0 commit comments

Comments
 (0)