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: api-reference/v1.0/resources/accesspackageassignmentrequest.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,16 +35,16 @@ In [Microsoft Entra Entitlement Management](entitlementmanagement-overview.md),
35
35
|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`. Read-only. Supports `$filter`.|
|requestType|accessPackageRequestType|The type of the request. The possible values are: `notSpecified`, `userAdd`, `UserExtend`, `userUpdate`, `userRemove`, `adminAdd`, `adminUpdate`, `adminRemove`, `systemAdd`, `systemUpdate`, `systemRemove`, `onBehalfAdd` (not supported), `unknownFutureValue`. Requests from the user have a **requestType** of `userAdd`, `userUpdate`, or `userRemove`. This property can't be changed once set.|
39
-
|schedule|[entitlementManagementSchedule](../resources/entitlementmanagementschedule.md)|The range of dates that access is to be assigned to the requestor. This property can't be changed once set, but a new schedule for an assignment can be included in another `userUpdate` or `UserExtend` or `adminUpdate` assignment request.|
38
+
|requestType|accessPackageRequestType|The type of the request. The possible values are: `notSpecified`, `userAdd`, `userUpdate`, `userRemove`, `adminAdd`, `adminUpdate`, `adminRemove`, `systemAdd`, `systemUpdate`, `systemRemove`, `onBehalfAdd` (not supported), `unknownFutureValue`. Use the `Prefer: include-unknown-enum-members` request header to get the following values in this [evolvable enum](/graph/best-practices-concept#handling-future-members-in-evolvable-enumerations): `approverRemove`. Requests from the user have a **requestType** of `userAdd`, `userUpdate`, or `userRemove`. This property can't be changed once set.|
39
+
|schedule|[entitlementManagementSchedule](../resources/entitlementmanagementschedule.md)|The range of dates that access is to be assigned to the requestor. This property can't be changed once set, but a new schedule for an assignment can be included in another `userUpdate` or `adminUpdate` assignment request.|
40
40
|state|accessPackageRequestState|The state of the request. The possible values are: `submitted`, `pendingApproval`, `delivering`, `delivered`, `deliveryFailed`, `denied`, `scheduled`, `canceled`, `partiallyDelivered`, `unknownFutureValue`. Read-only. Supports `$filter` (`eq`). |
41
41
|status|String|More information on the request processing status. Read-only.|
42
42
43
43
## Relationships
44
44
|Relationship|Type|Description|
45
45
|:---|:---|:---|
46
46
|accessPackage|[accessPackage](../resources/accesspackage.md)|The access package associated with the accessPackageAssignmentRequest. An access package defines the collections of resource roles and the policies for how one or more users can get access to those resources. Read-only. Nullable. <br/><br/> Supports `$expand`.|
47
-
|assignment|[accessPackageAssignment](../resources/accesspackageassignment.md)|For a **requestType** of `userAdd` or `adminAdd`, this is an access package assignment requested to be created. For a **requestType** of `userRemove`, `adminRemove` or `systemRemove`, this has the `id` property of an existing assignment to be removed. <br/><br/> Supports `$expand`.|
47
+
|assignment|[accessPackageAssignment](../resources/accesspackageassignment.md)|For a **requestType** of `userAdd` or `adminAdd`, this is an access package assignment requested to be created. For a **requestType** of `userRemove`, `adminRemove`, `approverRemove`, or `systemRemove`, this has the `id` property of an existing assignment to be removed. <br/><br/> Supports `$expand`.|
48
48
|requestor|[accessPackageSubject](../resources/accesspackagesubject.md)|The subject who requested or, if a direct assignment, was assigned. Read-only. Nullable. Supports `$expand`.|
Copy file name to clipboardExpand all lines: concepts/whats-new-overview.md
+60Lines changed: 60 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,66 @@ For details about previous updates to Microsoft Graph, see [Microsoft Graph what
20
20
21
21
## April 2026: New and generally available
22
22
23
+
### Identity and access | Governance
24
+
25
+
Added the `approverRemove` member to the **accessPackageRequestType** enumeration. For more information, see [accessPackageAssignmentRequest](/graph/api/resources/accesspackageassignmentrequest).
26
+
27
+
## February 2026: New and generally available
28
+
29
+
### Search
30
+
31
+
- Added the **Principal** and **principalCollection** data types to the [externalConnection](graph/api/resources/resources/externalconnectors-principal) to specify as the data type people property related items in the external connection.
32
+
33
+
- Added the **description** property to the [externalConnection properties](graph/api/resources/externalconnectors-property) to be add description to the schema properties in the external connection.
34
+
35
+
- Added more tags or semantic labels that can be added to **labels**[externalConnection property](graph/api/resources/externalconnectors-property) in the external connection schema. Labels help Microsoft 365 Copilot understand the semantics of the data in the connection and provide more relevant results.
36
+
37
+
- Added the **contentCategory** property to the [externalConnection](graph/api/resources/resources/externalconnectors-externalconnection) to specify the domain category of the content associated with the external connection for improved relevance and ranking.
38
+
39
+
### Files
40
+
41
+
Updated the admin consent requirement for the following delegated permissions related to SharePoint Embedded file storage container management:
42
+
- The `FileStorageContainerType.Manage.All` delegated permission no longer requires admin consent.
43
+
- The `FileStorageContainerTypeReg.Manage.All` delegated permission no longer requires admin consent.
44
+
45
+
### Groups
46
+
47
+
- Added the **resourceBehaviorOptions** and **resourceProvisioningOptions** properties to the [group](/graph/api/resources/group) resource. These properties enable you to specify group behaviors and associated resources for a Microsoft 365 group.
48
+
- Added a known issue: For soft deleted security groups, the **securityEnabled** property returns `false` instead of `true`. To identify the group type, use the **groupTypes** property where `["Unified"]` indicates a Microsoft 365 group and an empty array (`[]`) indicates a security group. For more information, see [Get deleted item](/graph/api/directory-deleteditems-get) and [List deleted items](/graph/api/directory-deleteditems-list).
49
+
50
+
### Identity and access | Identity and sign-in
51
+
52
+
- QR code authentication method in Microsoft Entra ID lets you manage the QR code authentication method for users, and how they can sign in with a QR code and PIN. The following key resources support this capability:
53
+
- The [qrCodePinAuthenticationMethod](/graph/api/resources/qrcodepinauthenticationmethod) resource and related APIs for managing QR code PIN authentication methods for users. This single-factor authentication method is designed for frontline workers and combines a QR code with a PIN. The following related resources were also added: [qrCode](/graph/api/resources/qrcode), [qrPin](/graph/api/resources/qrpin), and [qrCodeImageDetails](/graph/api/resources/qrcodeimagedetails).
54
+
- The [qrCodePinAuthenticationMethodConfiguration](/graph/api/resources/qrcodepinauthenticationmethodconfiguration) resource for managing the QR code authentication method policy for a tenant.
55
+
- Updated the [authenticationMethodModes](/graph/api/resources/authenticationmethodmodes) and [baseAuthenticationMethod](/graph/api/resources/baseauthenticationmethod) enumerations to add the `qrCodePin` member to support this new authentication method.
56
+
57
+
### Message trace
58
+
59
+
Use the message trace API to track the flow of email messages through your Exchange Online organization. For more information, see [exchangeMessageTrace](/graph/api/resources/exchangemessagetrace).
60
+
61
+
### Security | Data security and compliance
62
+
63
+
Added the `restrictWebGrounding` member to the [dlpAction](/graph/api/resources/enums-security#dlpaction-values) enumeration to support restricting web grounding actions in data loss prevention policies in Microsoft Purview.
64
+
65
+
### Security | Threat protection
66
+
67
+
Updated the admin consent requirement for the following delegated permissions related to threat submissions:
68
+
- The `ThreatSubmission.Read` delegated permission now requires admin consent.
69
+
- The `ThreatSubmission.ReadWrite` delegated permission now requires admin consent.
70
+
71
+
### Teamwork and communications | Administration
72
+
73
+
-[Get the policy ID](/graph/api/teamsadministration-teamspolicyassignment-getpolicyid) for a given policy name and policy type within Teams administration.
74
+
-[Assign a Teams policy](/graph/api/teamsadministration-teamspolicyuserassignment-assign) to a user using the user ID, policy type, and policy ID.
75
+
-[Unassign a Teams policy](/graph/api/teamsadministration-teamspolicyuserassignment-unassign) from a user using the user ID and policy type.
76
+
77
+
## February 2026: New in preview only
78
+
79
+
### Applications
80
+
81
+
Use the **requiredResourceAccess** property on [agentIdentityBlueprint](/graph/api/resources/agentidentityblueprint?view=graph-rest-beta&preserve-view=true) to specify the Microsoft Graph permissions (delegated scopes and app roles) required by the agent.
82
+
23
83
### Backup storage
24
84
25
85
- When a [protection policy is deactivated](/graph/api/protectionpolicybase-deactivate), backup activity stops immediately, no new backups are taken, and the protected resources are no longer covered by the policy. Any backups taken before deactivation are retained according to the retention policy, after which they're offboarded. You can restore data using previous restore points even after deactivation.
0 commit comments