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/beta/api/entitlementmanagement-list-accesspackageassignmentpolicies.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ GET /identityGovernance/entitlementManagement/accessPackageAssignmentPolicies
37
37
38
38
## Optional query parameters
39
39
40
-
This method supports the `$select`, `$filter` and `$expand` OData query parameters to help customize the response. For example, to retrieve an access package assignment policy with a specified display name, include `$filter=displayName eq 'Employee sales support'` in the query. For general information, see [OData query parameters](/graph/query-parameters).
40
+
This method supports the `$select`, `$filter` and `$expand` OData query parameters to help customize the response. For example, to retrieve an access package assignment policy with a specified display name, include `$filter=displayName eq 'Employee sales support'` in the query. To retrieve the access package assignment policies for an access package `136f166c-b85a-4403-85b1-656aa80d167a`, include `$filter=accesspackage/id eq '136f166c-b85a-4403-85b1-656aa80d167a'`. For general information, see [OData query parameters](/graph/query-parameters).
Copy file name to clipboardExpand all lines: api-reference/v1.0/api/entitlementmanagement-list-assignmentpolicies.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ GET /identityGovernance/entitlementManagement/assignmentPolicies
35
35
```
36
36
37
37
## Optional query parameters
38
-
This method supports some of the `$filter`, `$select`, and `$expand` OData query parameters to help customize the response. For example, to retrieve an access package assignment policy with a specified display name, include `$filter=displayName eq 'Employee sales support'` in the query. For general information, see [OData query parameters](/graph/query-parameters).
38
+
This method supports some of the `$filter`, `$select`, and `$expand` OData query parameters to help customize the response. For example, to retrieve an access package assignment policy with a specified display name, include `$filter=displayName eq 'Employee sales support'` in the query. To retrieve the access package assignment policies for an access package `136f166c-b85a-4403-85b1-656aa80d167a`, include `$filter=accesspackage/id eq '136f166c-b85a-4403-85b1-656aa80d167a'`. For general information, see [OData query parameters](/graph/query-parameters).
Copy file name to clipboardExpand all lines: concepts/change-notifications-delivery-webhooks.md
-3
Original file line number
Diff line number
Diff line change
@@ -66,9 +66,6 @@ When you [renew your subscription](#renew-a-subscription), your access token is
66
66
### Firewall configuration
67
67
You can configure the firewall that protects your endpoint to allow inbound connections only from Microsoft Graph, reducing further exposure to invalid change notifications. For a complete list of IP addresses used by Microsoft Graph to deliver change notifications, see [additional endpoints for Microsoft 365](/office365/enterprise/additional-office365-ip-addresses-and-urls).
68
68
69
-
> [!NOTE]
70
-
> The listed IP addresses that are used to deliver change notifications can be updated at any time without notice.
@@ -431,13 +433,15 @@ For notifications with resource data, the payload looks like the following. This
431
433
432
434
The decrypted notification payload looks like the following. The payload conforms to the [transcript](/graph/api/resources/calltranscript) schema. The payload is similar to the ones returned by GET operations.
433
435
436
+
>**Note:** The payload object shown here is shortened for readability.
@@ -488,16 +494,18 @@ For notifications with resource data, the payload looks like the following. This
488
494
489
495
The decrypted notification payload looks like the following. The payload conforms to the [recording](/graph/api/resources/callrecording) schema. The payload is similar to the ones returned by GET operations.
490
496
497
+
>**Note:** The payload object shown here is shortened for readability.
0 commit comments