Updates from: 06/25/2021 03:15:27
Service Microsoft Docs article Related commit history on GitHub Change details
v1.0 Directoryrole Delete Member https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/beta/api/directoryrole-delete-member.md
One of the following permissions is required to call this API. To learn more, in
<!-- { "blockType": "ignored" } --> ```http
-DELETE /directoryRoles/{role-objectId}/members/{id}/$ref
-DELETE /directoryRoles/roleTemplateId={role-templateId}/members/{id}/$ref
+DELETE /directoryRoles/{role-id}/members/{id}/$ref
+DELETE /directoryRoles/roleTemplateId={roleTemplateId}/members/{id}/$ref
``` ## Request headers
Do not supply a request body for this method.
## Response
-If successful, this method returns `204 No Content` response code. It does not return anything in the response body.
+If successful, this method returns a `204 No Content` response code. It does not return anything in the response body.
## Examples
DELETE https://graph.microsoft.com/beta/directoryRoles/f8e85ed8-f66f-4058-b170-3
HTTP/1.1 204 No Content ```
-### Example 2: Remove directory role member using role templateId
+### Example 2: Remove directory role member using roleTemplateId
#### Request
-Here is an example of the request. Replace `9f06204d-73c1-4d4c-880a-6edb90606fd8` with the value of your roleTemplateId and `bb165b45-151c-4cf6-9911-cd7188912848` with the **id** value of your user of directory object.
+The following is an example of the request. Replace `9f06204d-73c1-4d4c-880a-6edb90606fd8` with the value of your roleTemplateId and `bb165b45-151c-4cf6-9911-cd7188912848` with the **id** value of your user of directory object.
# [HTTP](#tab/http)
v1.0 Directoryrole Delta https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/beta/api/directoryrole-delta.md
includes the encoded, desired parameters.
## Optional query parameters
-This method supports OData Query Parameters to help customize the response.
+This method supports OData query parameters to help customize the response.
- You can use a `$select` query parameter as in any GET request to specify only the properties your need for best performance. The _id_ property is always returned.
Do not supply a request body for this method.
### Response
-If successful, this method returns `200 OK` response code and [directoryRole](../resources/directoryrole.md) collection object in the response body. The response also includes a nextLink URL or a deltaLink URL.
+If successful, this method returns a `200 OK` response code and [directoryRole](../resources/directoryrole.md) collection object in the response body. The response also includes a nextLink URL or a deltaLink URL.
- If a `nextLink` URL is returned, there are additional pages of data to be retrieved in the session. The application continues making requests using the `nextLink` URL until a `deltaLink` URL is included in the response.
See:</br>
- [Get incremental changes for users](/graph/delta-query-users) for an example requests.</br> ### Example
-##### Request
+#### Request
# [HTTP](#tab/http) <!-- {
GET https://graph.microsoft.com/beta/directoryRoles/delta
-##### Response
-Note: The response object shown here might be shortened for readability.
+#### Response
+>**Note:** The response object shown here might be shortened for readability.
<!-- { "blockType": "response", "truncated": true,
HTTP/1.1 200 OK
Content-type: application/json {
- "@odata.context":"https://graph.microsoft.com/beta/$metadata#directoryRoles",
- "@odata.nextLink":"https://graph.microsoft.com/beta/directoryRoles/delta?$skiptoken=pqwSUjGYvb3jQpbwVAwEL7yuI3dU1LecfkkfLPtnIjsXoYQp_dpA3cNJWc",
+ "@odata.context": "https://graph.microsoft.com/beta/$metadata#directoryRoles",
+ "@odata.nextLink": "https://graph.microsoft.com/beta/directoryRoles/delta?$skiptoken=pkXMyA5aFCIMmH1Kk1XEAnf2X-fodqXKXF03gYPQknSHRxogVsxvSq_26nhos-O2-shortened",
"value": [
- {
- "description": "description-value",
- "displayName": "displayName-value",
- "roleTemplateId": "roleTemplateId-value",
- "id": "id-value"
+ {
+ "description": "Device Administrators",
+ "displayName": "Azure AD Joined Device Local Administrator",
+ "roleTemplateId": "9f06204d-73c1-4d4c-880a-6edb90606fd8",
+ "id": "f8e85ed8-f66f-4058-b170-3efae8b9c6e5",
+ "members@delta": [
+ {
+ "@odata.type": "#microsoft.graph.user",
+ "id": "bb165b45-151c-4cf6-9911-cd7188912848",
+ "@removed": {
+ "reason": "deleted"
+ }
+ }
+ ]
} ] }
v1.0 Directoryrole Get https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/beta/api/directoryrole-get.md
One of the following permissions is required to call this API. To learn more, in
## HTTP request <!-- { "blockType": "ignored" } --> ```http
-GET /directoryRoles/{role-objectId}
-GET /directoryRoles/roleTemplateId={role-templateId}
+GET /directoryRoles/{role-id}
+GET /directoryRoles/roleTemplateId={roleTemplateId}
``` ## Optional query parameters
-This method does **not** support any [OData Query Parameters](/graph/query-parameters) to help customize the response (for example, `$filter` is not supported here).
+This method does **not** support any [OData query parameters](/graph/query-parameters) to help customize the response (for example, `$filter` is not supported here).
## Request headers | Name | Type | Description|
Do not supply a request body for this method.
If successful, this method returns a `200 OK` response code and [directoryRole](../resources/directoryrole.md) object in the response body. ## Examples
-### Example 1: Get the definition of a directory role using role objectId
+### Example 1: Get the definition of a directory role using role id
#### Request
-Here is an example of the request.
+The following is an example of the request.
# [HTTP](#tab/http) <!-- {
Content-type: application/json
```
-### Example 2: Get the definition of a directory role using role templateId
+### Example 2: Get the definition of a directory role using roleTemplateId
#### Request
-Here is an example of the request.
+The following is an example of the request.
v1.0 Directoryrole List Members https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/beta/api/directoryrole-list-members.md
One of the following permissions is required to call this API. To learn more, in
## HTTP request <!-- { "blockType": "ignored" } --> ```http
-GET /directoryRoles/{role-objectId}/members
-GET /directoryRoles/roleTemplateId={role-templateId}/members
+GET /directoryRoles/{role-id}/members
+GET /directoryRoles/roleTemplateId={roleTemplateId}/members
``` ## Optional query parameters
-This method supports the [OData Query Parameters](/graph/query-parameters) to help customize the response.
+This method supports the [OData query parameters](/graph/query-parameters) to help customize the response.
## Request headers | Name | Type | Description| |:--|:|:-|
Do not supply a request body for this method.
If successful, this method returns a `200 OK` response code and collection of [directoryObject](../resources/directoryobject.md) objects in the response body. ## Examples
-### Example 1: Get the members of a directory role using role objectId
+### Example 1: Get the members of a directory role using role id
#### Request Here is an example of the request.
Content-type: application/json
} ```
-### Example 2: Get the members of a directory role using role templateId
+### Example 2: Get the members of a directory role using roleTemplateId
#### Request
-Here is an example of the request.
+The following is an example of the request.
# [HTTP](#tab/http)
v1.0 Directoryrole List Scopedmembers https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/beta/api/directoryrole-list-scopedmembers.md
+
+ Title: "List scopedMembers for a directory role"
+description: "Retrieve a list of scopedRoleMembership objects for a directory role."
+
+localization_priority: Normal
++
+# List scopedMembers for a directory role
+
+Namespace: microsoft.graph
++
+Retrieve a list of [scopedRoleMembership](../resources/scopedrolemembership.md) objects for a directory role.
+## Permissions
+One of the following permissions is required to call this API. To learn more, including how to choose permissions, see [Permissions](/graph/permissions-reference).
+
+|Permission type | Permissions (from least to most privileged) |
+|:--|:|
+|Delegated (work or school account) | RoleManagement.Read.Directory, Directory.Read.All, RoleManagement.ReadWrite.Directory, Directory.ReadWrite.All, Directory.AccessAsUser.All |
+|Delegated (personal Microsoft account) | Not supported. |
+|Application | RoleManagement.Read.Directory, Directory.Read.All, RoleManagement.ReadWrite.Directory, Directory.ReadWrite.All |
+
+## HTTP request
+<!-- { "blockType": "ignored" } -->
+```http
+GET /directoryroles/{role-id}/scopedMembers
+GET /directoryroles/roleTemplateId={roleTemplateId}/scopedMembers
+```
+## Optional query parameters
+This method supports the [OData query parameters](/graph/query-parameters) to help customize the response.
+
+## Request headers
+| Name |Description|
+|:-|:-|
+| Authorization | Bearer {token}. Required. |
+
+## Request body
+Do not supply a request body for this method.
+
+## Response
+
+If successful, this method returns a `200 OK` response code and a collection of [scopedRoleMembership](../resources/scopedrolemembership.md) objects in the response body.
+## Examples
+
+### Example 1: Get the scoped members of a directory role using role id
+
+#### Request
+The following is an example of a request for a directory role **id** `41d12a2f-caa8-4e3e-ba14-05e5102ce085`.
+
+# [HTTP](#tab/http)
+<!-- {
+ "blockType": "request",
+ "name": "get_scopedmembers_directoryrole"
+}-->
+```msgraph-interactive
+GET https://graph.microsoft.com/beta/directoryRoles/41d12a2f-caa8-4e3e-ba14-05e5102ce085/scopedMembers
+```
+# [C#](#tab/csharp)
+
+# [JavaScript](#tab/javascript)
+
+# [Objective-C](#tab/objc)
+
+# [Java](#tab/java)
+++
+#### Response
+The following example shows the response.
+>**Note:** The response object shown here might be shortened for readability.
+<!-- {
+ "blockType": "response",
+ "truncated": true,
+ "@odata.type": "microsoft.graph.scopedRoleMembership",
+ "isCollection": true
+} -->
+```http
+HTTP/1.1 200 OK
+Content-type: application/json
+
+{
+ "@odata.context": "https://graph.microsoft.com/beta/$metadata#scopedRoleMemberships",
+ "value": [
+ {
+ "id": "LyrRQajKPk66FAXlECzghXFuYtw3SOtAvkq8KdiKEXiTwZeOU-r8RIHrq2vQ4F1wU",
+ "roleId": "41d12a2f-caa8-4e3e-ba14-05e5102ce085",
+ "administrativeUnitId": "dc626e71-4837-40eb-be4a-bc29d88a1178",
+ "roleMemberInfo": {
+ "id": "8e97c193-ea53-44fc-81eb-ab6bd0e05d70",
+ "displayName": "Adele Vance"
+ }
+ }
+ ]
+}
+```
+
+### Example 2: Get the scoped members of a directory role using roleTemplateId
+
+#### Request
+The following is an example of a request for a directory role with **roleTemplateId** `fdd7a751-b60b-444a-984c-02652fe8fa1c`.
+
+<!-- {
+ "blockType": "request",
+ "name": "get_scopedmembers_directoryrole_templateId"
+}-->
+```msgraph-interactive
+GET https://graph.microsoft.com/beta/directoryRoles/roleTemplateId=fdd7a751-b60b-444a-984c-02652fe8fa1c/scopedMembers
+```
+
+#### Response
+The following example shows the response.
+>**Note:** The response object shown here might be shortened for readability.
+<!-- {
+ "blockType": "response",
+ "truncated": true,
+ "@odata.type": "microsoft.graph.scopedRoleMembership",
+ "isCollection": true
+} -->
+```http
+HTTP/1.1 200 OK
+Content-type: application/json
+
+{
+ "@odata.context": "https://graph.microsoft.com/beta/$metadata#scopedRoleMemberships",
+ "value": [
+ {
+ "id": "LyrRQajKPk66FAXlECzghXFuYtw3SOtAvkq8KdiKEXiTwZeOU-r8RIHrq2vQ4F1wU",
+ "roleId": "41d12a2f-caa8-4e3e-ba14-05e5102ce085",
+ "administrativeUnitId": "dc626e71-4837-40eb-be4a-bc29d88a1178",
+ "roleMemberInfo": {
+ "id": "8e97c193-ea53-44fc-81eb-ab6bd0e05d70",
+ "displayName": "Adele Vance"
+ }
+ }
+ ]
+}
+```
+
+<!-- uuid: 8fcb5dbc-d5aa-4681-8e31-b001d5168d79
+2015-10-25 14:57:30 UTC -->
+<!--
+{
+ "type": "#page.annotation",
+ "description": "List scopedmembers",
+ "keywords": "",
+ "section": "documentation",
+ "tocPath": "",
+ "suppressions": [
+ ]
+}
+-->
v1.0 Directoryrole Post Members https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/beta/api/directoryrole-post-members.md
One of the following permissions is required to call this API. To learn more, in
## HTTP request <!-- { "blockType": "ignored" } --> ```http
-POST /directoryRoles/{role-objectId}/members/$ref
-POST /directoryRoles/roleTemplateId={role-templateId}/members/$ref
+POST /directoryRoles/{role-id}/members/$ref
+POST /directoryRoles/roleTemplateId={roleTemplateId}/members/$ref
``` ## Request headers | Name | Type | Description|
Content-length: 30
HTTP/1.1 204 No content ```
-### Example 3: Add a new member to a directory role using role templateId
+### Example 3: Add a new member to a directory role using roleTemplateId
#### Request In this request, replace `88d8e3e3-8f55-4a1e-953a-9b9898b8876b` with the value of the **roleTemplateId** for the directory role you wish to assign to the user or directory object. Replace `bb165b45-151c-4cf6-9911-cd7188912848` with the **id** value of your user or directory object.
v1.0 Signin Get https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/beta/api/signin-get.md
One of the following permissions is required to call this API. To learn more, in
| Delegated (personal Microsoft account) | Not supported | | Application | AuditLog.Read.All, Directory.Read.All |
-In addition, apps must be [properly registered](/azure/active-directory/active-directory-reporting-api-prerequisites-azure-portal) to Azure AD.
+Apps must be [properly registered](/azure/active-directory/active-directory-reporting-api-prerequisites-azure-portal) to Azure AD.
+
+In addition to the delegated permissions, the signed-in user needs to belong to one of the following directory roles that allow them to read sign-in reports. To learn more about directory roles, see [Azure AD built-in roles](/azure/active-directory/roles/permissions-reference):
++ Global Administrator++ Global Reader++ Reports Reader++ Security Administrator++ Security Operator++ Security Reader ## HTTP request
v1.0 Signin List https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/beta/api/signin-list.md
One of the following permissions is required to call this API. To learn more, in
| Delegated (personal Microsoft account) | Not supported | | Application | AuditLog.Read.All, Directory.Read.All |
-In addition, apps must be properly registered to Azure Active Directory.
+Apps must be [properly registered](/azure/active-directory/active-directory-reporting-api-prerequisites-azure-portal) to Azure AD.
+
+In addition to the delegated permissions, the signed-in user needs to belong to one of the following directory roles that allow them to read sign-in reports. To learn more about directory roles, see [Azure AD built-in roles](/azure/active-directory/roles/permissions-reference):
++ Global Administrator++ Global Reader++ Reports Reader++ Security Administrator++ Security Operator++ Security Reader ## HTTP request <!-- { "blockType": "ignored" } -->
v1.0 Alerttrigger https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/beta/resources/alerttrigger.md
Contains information about the properties that triggered a detection (properties
| Property | Type|Description| |:|:--|:-| |name|String|Name of the property serving as a detection trigger.|
-|type|String|Type of the property in the key:value pair for interpretation. For example, String, Boolean, etc.|
+|type|String|Type of the property in the key:value pair for interpretation. For example, String, Boolean etc.|
|value|String|Value of the property serving as a detection trigger.| ## JSON representation
The following is a JSON representation of the resource.
"type": "String", "value": "String" }- ``` ## Example
The following is a JSON representation of the resource.
"type": "String", "value": "10.154.9.40" }- ``` <!-- uuid: 8fcb5dbc-d5aa-4681-8e31-b001d5168d79
v1.0 Azure Ad Auditlog Overview https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/beta/resources/azure-ad-auditlog-overview.md
To learn more, see [Azure AD pricing](https://azure.microsoft.com/pricing/detail
## Next steps - [Register your app](/azure/active-directory/active-directory-reporting-api-prerequisites-azure-portal) to satisfy report prerequisites. -- Learn from [audit log](/azure/active-directory/active-directory-reporting-api-audit-samples) and [sign-in samples](/azure/active-directory/active-directory-reporting-api-sign-in-activity-samples).
+- To learn how to retrieve audit logs while authenticated using certificates, see [Tutorial: Get data using the Azure Active Directory reporting API with certificates](/azure/active-directory/reports-monitoring/tutorial-access-api-with-certificates).
- Review the [directoryAudit](directoryaudit.md) resource and actions. - Review the [signIn](signin.md) resource and actions. - Review the [provisioningObjectSummary](provisioningobjectsummary.md) resource.
v1.0 Azure Ad Overview https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/beta/resources/azure-ad-overview.md
Directory resources and APIs can open up new ways for you to engage with users a
- Drill down on the methods and properties of the resources most helpful to your scenario. - Try the API in the [Graph Explorer](https://developer.microsoft.com/graph/graph-explorer).
-Need more ideas? See [how some of our partners are using Microsoft Graph](https://developer.microsoft.com/graph/graph/examples#partners).
+Need more ideas? See [how some of our partners are using Microsoft Graph](https://developer.microsoft.com/graph/partners).
v1.0 Booking Api Overview https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/beta/resources/booking-api-overview.md
Title: "Use the Microsoft Bookings API in Microsoft Graph"
-description: " > **Important:** APIs under the /beta version in Microsoft Graph are in preview and are subject to change. Use of these APIs in production applications is not supported."
+description: "Microsoft Bookings lets enterprise organization and small business owners manage customer bookings and information with minimal setup."
localization_priority: Priority ms.prod: "bookings"
Find out about the [latest new features and updates](/graph/whats-new-overview)
## See also - Try the API in the [Graph Explorer](https://developer.microsoft.com/graph/graph-explorer).-- See [how some of our partners are using Microsoft Graph](https://developer.microsoft.com/graph/graph/examples#partners).
+- See [how some of our partners are using Microsoft Graph](https://developer.microsoft.com/graph/partners).
- Learn how to choose [permissions](/graph/permissions-reference) in Microsoft Graph.
v1.0 Changenotification https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/beta/resources/changenotification.md
None.
| clientState | string | Value of the **clientState** property sent specified in the subscription request (if any). The maximum length is 255 characters. The client can check whether the change notification came from the service by comparing the values of the **clientState** property. The value of the **clientState** property sent with the subscription is compared with the value of the **clientState** property received with each change notification. Optional. | | encryptedContent | [changeNotificationEncryptedContent](changenotificationencryptedcontent.md) | (Preview) Encrypted content attached with the change notification. Only provided if **encryptionCertificate** and **includeResourceData** were defined during the subscription request and if the resource supports it. Optional. | | id | string | Unique ID for the notification. Optional. |
-| lifecycleEvent | lifecycleEventType | The type of lifecycle notification if the current notification is a lifecycle notification. Optional. Supported values are `missed`, `removed`, `reauthorizationRequired`. |
+| lifecycleEvent | lifecycleEventType | The type of lifecycle notification if the current notification is a lifecycle notification. Optional. Supported values are `missed`, `subscriptionRemoved`, `reauthorizationRequired`. |
| resource | string | The URI of the resource that emitted the change notification relative to `https://graph.microsoft.com`. Required. | | resourceData | [resourceData](resourcedata.md) | The content of this property depends on the type of resource being subscribed to. Required. | | subscriptionExpirationDateTime | DateTimeOffset | The expiration time for the subscription. Required. |
v1.0 Directoryrole https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/beta/resources/directoryrole.md
This resource supports:
|[Add member](../api/directoryrole-post-members.md) |[directoryObject](directoryobject.md)| Add a user to the directory role by posting to the members navigation property.| |[List members](../api/directoryrole-list-members.md) |[directoryObject](directoryobject.md) collection| Get the users that are members of the directory role from the members navigation property.| |[Remove a member](../api/directoryrole-delete-member.md) |[directoryObject](directoryobject.md)| Remove a user from the directory role.|
-|[List scoped-role members](../api/directoryrole-list-members.md) |[scopedRoleMembership](scopedrolemembership.md) collection| List the members of this directory role that are scoped to [administrative units](administrativeunit.md), through the scopedRoleMembership resource collection.|
+|[Activate directoryRole](../api/directoryrole-post-directoryroles.md) |[directoryRole](directoryrole.md) | Activate a directory role.|
+|[List scopeMembers](../api/directoryrole-list-scopedmembers.md) |[scopedRoleMembership](scopedrolemembership.md) collection| List the members of this directory role that are scoped to [administrative units](administrativeunit.md), through the scopedRoleMembership resource collection.|
|[delta](../api/directoryrole-delta.md)|directoryRole collection| Get incremental changes for directory roles. | ## Properties
v1.0 Mail Api Overview https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/beta/resources/mail-api-overview.md
The mail API can open up new ways for you to engage with users:
- Drill down on the [methods](../resources/message.md#methods), [properties](../resources/message.md#properties), and [relationships](../resources/message.md#relationships) of the [message](../resources/message.md) and [mailFolder](../resources/mailfolder.md) resources. - Try the API in the [Graph Explorer](https://developer.microsoft.com/graph/graph-explorer).
-Need more ideas? See [how some of our partners are using Microsoft Graph](https://developer.microsoft.com/graph/graph/examples#partners).
+Need more ideas? See [how some of our partners are using Microsoft Graph](https://developer.microsoft.com/graph/partners).
v1.0 Report https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/beta/resources/report.md
Reports resources and APIs can open up new ways for you to engage with users and
- Drill down on the methods and properties of the resources most helpful to your scenario. - Try the API in the [Graph Explorer](https://developer.microsoft.com/graph/graph-explorer).
-Need more ideas? See [how some of our partners are using Microsoft Graph](https://developer.microsoft.com/graph/graph/examples#partners).
+Need more ideas? See [how some of our partners are using Microsoft Graph](https://developer.microsoft.com/graph/partners).
v1.0 Security Api Overview https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/beta/resources/security-api-overview.md
The Microsoft Graph Security API can open up new ways for you to engage with dif
- Try the API in the [Graph Explorer](https://developer.microsoft.com/graph/graph-explorer). Under **Sample Queries**, choose **show more samples** and set the Security category to **on**. - Try [subscribing to and receiving notifications](/graph/webhooks) on entity changes.
-Need more ideas? See [how some of our partners are using Microsoft Graph](https://developer.microsoft.com/graph/graph/examples#partners).
+Need more ideas? See [how some of our partners are using Microsoft Graph](https://developer.microsoft.com/graph/partners).
## See also
v1.0 User https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/beta/resources/user.md
This resource supports:
| companyName | String | The company name which the user is associated. This property can be useful for describing the company that an external user comes from. The maximum length of the company name is 64 characters.<br><br>Supports `$filter` (`eq`, `ne`, `NOT`, `ge`, `le`, `in`, `startsWith`).| | consentProvidedForMinor | [consentProvidedForMinor](#consentprovidedforminor-values) | Sets whether consent has been obtained for minors. Allowed values: `null`, `granted`, `denied` and `notRequired`. Refer to the [legal age group property definitions](#legal-age-group-property-definitions) for further information. <br><br>Supports `$filter` (`eq`, `ne`, `NOT`, and `in`).| | country | String | The country/region in which the user is located; for example, `US` or `UK`. Maximum length is 128 characters. <br><br>Supports `$filter` (`eq`, `ne`, `NOT`, `ge`, `le`, `in`, `startsWith`). |
-| createdDateTime | DateTimeOffset | The date and time the user was created. The value cannot be modified and is automatically populated when the entity is created. The DateTimeOffset type represents date and time information using ISO 8601 format and is always in UTC time. Property is nullable. A null value indicates that an accurate creation time couldn't be determined for the user. Read-only. <br><br>Supports `$filter` (`eq`, `ne`, `NOT` , `ge`, `le`, and `in` operators) and `$orderBy`. |
+| createdDateTime | DateTimeOffset | The date and time the user was created. The value cannot be modified and is automatically populated when the entity is created. The DateTimeOffset type represents date and time information using ISO 8601 format and is always in UTC time. Property is nullable. A null value indicates that an accurate creation time couldn't be determined for the user. Read-only. <br><br>Supports `$filter` (`eq`, `ne`, `NOT` , `ge`, `le`, and `in` operators). |
| creationType | String | Indicates whether the user account was created as a regular school or work account (`null`), an external account (`Invitation`), a local account for an Azure Active Directory B2C tenant (`LocalAccount`) or self-service sign-up using email verification (`EmailVerified`). Read-only. <br><br>Supports `$filter` (`eq`, `ne`, `NOT`, and `in`). |
-| deletedDateTime | DateTimeOffset | The date and time the user was deleted. <br><br>Supports `$filter` (`eq`, `ne`, `NOT`, `ge`, `le`, and `in`) and `$orderBy`. |
+| deletedDateTime | DateTimeOffset | The date and time the user was deleted. <br><br>Supports `$filter` (`eq`, `ne`, `NOT`, `ge`, `le`, and `in`). |
| department | String | The name for the department in which the user works. Maximum length is 64 characters.<br><br>Supports `$filter` (`eq`, `ne`, `NOT` , `ge`, `le`, and `in` operators). | | displayName | String | The name displayed in the address book for the user. This value is usually the combination of the user's first name, middle initial, and last name. This property is required when a user is created and it cannot be cleared during updates. Maximum length is 256 characters. <br><br>Supports `$filter` (`eq`, `ne`, `NOT` , `ge`, `le`, `in`, `startsWith`), `$orderBy`, and `$search`.| | employeeHireDate | DateTimeOffset | The date and time when the user was hired or will start work in case of a future hire. <br><br>Supports `$filter` (`eq`, `ne`, `NOT` , `ge`, `le`, `in`).|
v1.0 Directoryrole Delete Member https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/v1.0/api/directoryrole-delete-member.md
One of the following permissions is required to call this API. To learn more, in
<!-- { "blockType": "ignored" } --> ```http
-DELETE /directoryRoles/{role-objectId}/members/{id}/$ref
-DELETE /directoryRoles/roleTemplateId={role-templateId}/members/{id}/$ref
+DELETE /directoryRoles/{role-id}/members/{id}/$ref
+DELETE /directoryRoles/roleTemplateId={roleTemplateId}/members/{id}/$ref
``` ## Request headers
Do not supply a request body for this method.
## Response
-If successful, this method returns `204 No Content` response code. It does not return anything in the response body.
+If successful, this method returns a `204 No Content` response code. It does not return anything in the response body.
## Examples
-### Example 1: Remove directory role member using role objectId
+### Example 1: Remove directory role member using role id
#### Request
DELETE https://graph.microsoft.com/v1.0/directoryRoles/f8e85ed8-f66f-4058-b170-3
#### Response-
-Here is an example of the response.
<!-- { "blockType": "response", "truncated": true
Here is an example of the response.
HTTP/1.1 204 No Content ```
-### Example 2: Remove directory role member using role templateId
+### Example 2: Remove directory role member using roleTemplateId
#### Request
-Here is an example of the request. Replace `9f06204d-73c1-4d4c-880a-6edb90606fd8` with the value of your roleTemplateId and `bb165b45-151c-4cf6-9911-cd7188912848` with the **id** value of your user of directory object.
+The following is an example of the request. Replace `9f06204d-73c1-4d4c-880a-6edb90606fd8` with the value of your roleTemplateId and `bb165b45-151c-4cf6-9911-cd7188912848` with the **id** value of your user of directory object.
# [HTTP](#tab/http) <!-- {
DELETE https://graph.microsoft.com/v1.0/directoryRoles/roleTemplateId=9f06204d-7
#### Response-
-Here is an example of the response.
<!-- { "blockType": "response", "truncated": true
v1.0 Directoryrole Delta https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/v1.0/api/directoryrole-delta.md
Do not supply a request body for this method.
### Response
-If successful, this method returns `200 OK` response code and [directoryRole](../resources/directoryrole.md) collection object in the response body. The response also includes a `nextLink` URL or a `deltaLink` URL.
+If successful, this method returns a `200 OK` response code and [directoryRole](../resources/directoryrole.md) collection object in the response body. The response also includes a `nextLink` URL or a `deltaLink` URL.
- If a `nextLink` URL is returned, there are additional pages of data to be retrieved in the session. The application continues making requests using the `nextLink` URL until a `deltaLink` URL is included in the response.
If successful, this method returns `200 OK` response code and [directoryRole](..
### Example
-##### Request
+#### Request
# [HTTP](#tab/http)
GET https://graph.microsoft.com/v1.0/directoryRoles/delta
-##### Response
+#### Response
-Note: The response object shown here might be shortened for readability.
+>**Note:** The response object shown here might be shortened for readability.
<!-- { "blockType": "response", "truncated": true,
HTTP/1.1 200 OK
Content-type: application/json {
- "@odata.context":"https://graph.microsoft.com/v1.0/$metadata#directoryRoles",
- "@odata.nextLink":"https://graph.microsoft.com/v1.0/directoryRoles/delta?$skiptoken=pqwSUjGYvb3jQpbwVAwEL7yuI3dU1LecfkkfLPtnIjsXoYQp_dpA3cNJWc",
+ "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#directoryRoles",
+ "@odata.nextLink": "https://graph.microsoft.com/v1.0/directoryRoles/delta?$skiptoken=pkXMyA5aFCIMmH1Kk1XEAnf2X-fodqXKXF03gYPQknSHRxogVsxvSq_26nhos-O2-shortened",
"value": [
- {
- "description": "description-value",
- "displayName": "displayName-value",
- "roleTemplateId": "roleTemplateId-value",
- "id": "id-value"
+ {
+ "description": "Device Administrators",
+ "displayName": "Azure AD Joined Device Local Administrator",
+ "roleTemplateId": "9f06204d-73c1-4d4c-880a-6edb90606fd8",
+ "id": "f8e85ed8-f66f-4058-b170-3efae8b9c6e5",
+ "members@delta": [
+ {
+ "@odata.type": "#microsoft.graph.user",
+ "id": "bb165b45-151c-4cf6-9911-cd7188912848",
+ "@removed": {
+ "reason": "deleted"
+ }
+ }
+ ]
} ] }
v1.0 Directoryrole Get https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/v1.0/api/directoryrole-get.md
One of the following permissions is required to call this API. To learn more, in
## HTTP request <!-- { "blockType": "ignored" } --> ```http
-GET /directoryRoles/{role-objectId}
-GET /directoryRoles/roleTemplateId={role-templateId}
+GET /directoryRoles/{role-id}
+GET /directoryRoles/roleTemplateId={roleTemplateId}
``` ## Optional query parameters
-This method does **not** support any [OData Query Parameters](/graph/query-parameters) to help customize the response (for example, `$filter` is not supported here).
+This method does **not** support any [OData query parameters](/graph/query-parameters) to help customize the response (for example, `$filter` is not supported here).
## Request headers | Name | Type | Description|
Do not supply a request body for this method.
If successful, this method returns a `200 OK` response code and [directoryRole](../resources/directoryrole.md) object in the response body. ## Examples
-### Example 1: Get the definition of a directory role using role objectId
+### Example 1: Get the definition of a directory role using role id
#### Request
Content-type: application/json
} ```
-### Example 2: Get the definition of a directory role using role templateId
+### Example 2: Get the definition of a directory role using roleTemplateId
#### Request
v1.0 Directoryrole List Members https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/v1.0/api/directoryrole-list-members.md
One of the following permissions is required to call this API. To learn more, in
## HTTP request <!-- { "blockType": "ignored" } --> ```http
-GET /directoryRoles/{role-objectId}/members
-GET /directoryRoles/roleTemplateId={role-templateId}/members
+GET /directoryRoles/{role-id}/members
+GET /directoryRoles/roleTemplateId={roleTemplateId}/members
``` ## Optional query parameters
-This method supports the [OData Query Parameters](/graph/query-parameters) to help customize the response.
+This method supports the [OData query parameters](/graph/query-parameters) to help customize the response.
## Request headers | Name | Type | Description| |:--|:|:-|
Do not supply a request body for this method.
If successful, this method returns a `200 OK` response code and collection of [directoryObject](../resources/directoryobject.md) objects in the response body. ## Examples
-### Example 1: Get the members of a directory role using role objectId
+### Example 1: Get the members of a directory role using role id
#### Request
Content-type: application/json
] } ```
-### Example 2: Get the members of a directory role using role templateId
+### Example 2: Get the members of a directory role using roleTemplateId
##### Request
v1.0 Directoryrole List Scopedmembers https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/v1.0/api/directoryrole-list-scopedmembers.md
+
+ Title: "List scopedMembers for a directory role"
+description: "Retrieve a list of scopedRoleMembership objects for a directory role."
+
+localization_priority: Normal
++
+# List scopedMembers for a directory role
+
+Namespace: microsoft.graph
+
+Retrieve a list of [scopedRoleMembership](../resources/scopedrolemembership.md) objects for a directory role.
+## Permissions
+One of the following permissions is required to call this API. To learn more, including how to choose permissions, see [Permissions](/graph/permissions-reference).
+
+|Permission type | Permissions (from least to most privileged) |
+|:--|:|
+|Delegated (work or school account) | RoleManagement.Read.Directory, Directory.Read.All, RoleManagement.ReadWrite.Directory, Directory.ReadWrite.All, Directory.AccessAsUser.All |
+|Delegated (personal Microsoft account) | Not supported. |
+|Application | RoleManagement.Read.Directory, Directory.Read.All, RoleManagement.ReadWrite.Directory, Directory.ReadWrite.All |
+
+## HTTP request
+<!-- { "blockType": "ignored" } -->
+```http
+GET /directoryroles/{role-id}/scopedMembers
+GET /directoryroles/roleTemplateId={roleTemplateId}/scopedMembers
+```
+## Optional query parameters
+This method supports the [OData query parameters](/graph/query-parameters) to help customize the response.
+
+## Request headers
+| Name |Description|
+|:-|:-|
+| Authorization | Bearer {token}. Required. |
+
+## Request body
+Do not supply a request body for this method.
+
+## Response
+
+If successful, this method returns a `200 OK` response code and a collection of [scopedRoleMembership](../resources/scopedrolemembership.md) objects in the response body.
+
+## Examples
+
+### Example 1: Get the members of a directory role using role id
+
+#### Request
+The following is an example of a request for a directory role **id** `41d12a2f-caa8-4e3e-ba14-05e5102ce085`.
+
+<!-- {
+ "blockType": "request",
+ "name": "get_scopedmembers_directoryrole"
+}-->
+```msgraph-interactive
+GET https://graph.microsoft.com/v1.0/directoryRoles/41d12a2f-caa8-4e3e-ba14-05e5102ce085/scopedMembers
+```
+
+#### Response
+The following example shows the response.
+
+>**Note:** The response object shown here might be shortened for readability.
+<!-- {
+ "blockType": "response",
+ "truncated": true,
+ "@odata.type": "microsoft.graph.scopedRoleMembership",
+ "isCollection": true
+} -->
+```http
+HTTP/1.1 200 OK
+Content-type: application/json
+
+{
+ "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#scopedRoleMemberships",
+ "value": [
+ {
+ "id": "LyrRQajKPk66FAXlECzghXFuYtw3SOtAvkq8KdiKEXiTwZeOU-r8RIHrq2vQ4F1wU",
+ "roleId": "41d12a2f-caa8-4e3e-ba14-05e5102ce085",
+ "administrativeUnitId": "dc626e71-4837-40eb-be4a-bc29d88a1178",
+ "roleMemberInfo": {
+ "id": "8e97c193-ea53-44fc-81eb-ab6bd0e05d70",
+ "displayName": "Adele Vance"
+ }
+ }
+ ]
+}
+```
++
+### Example 2: Get the scoped members of a directory role using roleTemplateId
+
+#### Request
+The following is an example of a request for a directory role with **roleTemplateId** `fdd7a751-b60b-444a-984c-02652fe8fa1c`.
+
+<!-- {
+ "blockType": "request",
+ "name": "get_scopedmembers_directoryrole_templateId"
+}-->
+```msgraph-interactive
+GET https://graph.microsoft.com/v1.0/directoryRoles/roleTemplateId=fdd7a751-b60b-444a-984c-02652fe8fa1c/scopedMembers
+```
+
+#### Response
+The following example shows the response.
+>**Note:** The response object shown here might be shortened for readability.
+<!-- {
+ "blockType": "response",
+ "truncated": true,
+ "@odata.type": "microsoft.graph.scopedRoleMembership",
+ "isCollection": true
+} -->
+```http
+HTTP/1.1 200 OK
+Content-type: application/json
+
+{
+ "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#scopedRoleMemberships",
+ "value": [
+ {
+ "id": "LyrRQajKPk66FAXlECzghXFuYtw3SOtAvkq8KdiKEXiTwZeOU-r8RIHrq2vQ4F1wU",
+ "roleId": "41d12a2f-caa8-4e3e-ba14-05e5102ce085",
+ "administrativeUnitId": "dc626e71-4837-40eb-be4a-bc29d88a1178",
+ "roleMemberInfo": {
+ "id": "8e97c193-ea53-44fc-81eb-ab6bd0e05d70",
+ "displayName": "Adele Vance"
+ }
+ }
+ ]
+}
+```
+
+<!-- uuid: 8fcb5dbc-d5aa-4681-8e31-b001d5168d79
+2015-10-25 14:57:30 UTC -->
+<!--
+{
+ "type": "#page.annotation",
+ "description": "List scopedmembers",
+ "keywords": "",
+ "section": "documentation",
+ "tocPath": "",
+ "suppressions": [
+ ]
+}
+-->
v1.0 Directoryrole Post Members https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/v1.0/api/directoryrole-post-members.md
One of the following permissions is required to call this API. To learn more, in
## HTTP request <!-- { "blockType": "ignored" } --> ```http
-POST /directoryRoles/{role-objectId}/members/$ref
-POST /directoryRoles/roleTemplateId={role-templateId}/members/$ref
+POST /directoryRoles/{role-id}/members/$ref
+POST /directoryRoles/roleTemplateId={roleTemplateId}/members/$ref
``` ## Request headers
If successful, this method returns `204 No Content` response code.
## Examples
-### Example 1: Add a new member to a directory role using role objectId
+### Example 1: Add a new member to a directory role using role id
In this request, replace `fe8f10bf-c9c2-47eb-95cb-c26cc85f1830` with the **id** value for the directory role you wish to assign to the user or directory object. Replace `15c1a2d5-9101-44b2-83ab-885db8a647ca` with the **id** value of your user or directory object.
Content-type: text/plain
```
-### Example 2: Add a new member to a directory role using role templateId
+### Example 2: Add a new member to a directory role using roleTemplateId
In this request, replace `88d8e3e3-8f55-4a1e-953a-9b9898b8876b` with the value of the **roleTemplateId** for the directory role you wish to assign to the user or directory object. Replace `bb165b45-151c-4cf6-9911-cd7188912848` with the **id** value of your user or directory object.
v1.0 Signin Get https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/v1.0/api/signin-get.md
One of the following permissions is required to call this API. To learn more, in
|Delegated (personal Microsoft account) | Not supported | |Application | AuditLog.Read.All and Directory.Read.All |
+Apps must be [properly registered](/azure/active-directory/active-directory-reporting-api-prerequisites-azure-portal) to Azure AD.
+
+In addition to the delegated permissions, the signed-in user needs to belong to one of the following directory roles that allow them to read sign-in reports. To learn more about directory roles, see [Azure AD built-in roles](/azure/active-directory/roles/permissions-reference):
++ Global Administrator++ Global Reader++ Reports Reader++ Security Administrator++ Security Operator++ Security Reader+ ## HTTP request <!-- { "blockType": "ignored" } -->
v1.0 Signin List https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/v1.0/api/signin-list.md
One of the following permissions is required to call this API. To learn more, in
|Delegated (personal Microsoft account) | Not supported | |Application | AuditLog.Read.All and Directory.Read.All |
+Apps must be [properly registered](/azure/active-directory/active-directory-reporting-api-prerequisites-azure-portal) to Azure AD.
+
+In addition to the delegated permissions, the signed-in user needs to belong to one of the following directory roles that allow them to read sign-in reports. To learn more about directory roles, see [Azure AD built-in roles](/azure/active-directory/roles/permissions-reference):
++ Global Administrator++ Global Reader++ Reports Reader++ Security Administrator++ Security Operator++ Security Reader+ ## HTTP request <!-- { "blockType": "ignored" } -->
v1.0 Alerttrigger https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/v1.0/resources/alerttrigger.md
Contains information about the properties that triggered a detection (properties
| Property | Type|Description| |:|:--|:-| |name|String|Name of the property serving as a detection trigger.|
-|type|String|Type of the property in the key:value pair for interpretation. For example, String, Boolean, etc.|
+|type|String|Type of the property in the key:value pair for interpretation. For example, String, Boolean etc.|
|value|String|Value of the property serving as a detection trigger.| ## JSON representation
The following is a JSON representation of the resource.
"type": "String", "value": "String" }- ``` ## Example
The following is a JSON representation of the resource.
"type": "String", "value": "10.154.9.40" }- ``` <!-- uuid: 8fcb5dbc-d5aa-4681-8e31-b001d5168d79
v1.0 Azure Ad Auditlog Overview https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/v1.0/resources/azure-ad-auditlog-overview.md
To learn more, see [Azure AD pricing](https://azure.microsoft.com/pricing/detail
## Next Steps - [Register your app](/azure/active-directory/active-directory-reporting-api-prerequisites-azure-portal) to satisfy report prerequisites. -- Learn from [audit log](/azure/active-directory/active-directory-reporting-api-audit-samples) and [sign-in samples](/azure/active-directory/active-directory-reporting-api-sign-in-activity-samples).
+- To learn how to retrieve audit logs while authenticated using certificates, see [Tutorial: Get data using the Azure Active Directory reporting API with certificates](/azure/active-directory/reports-monitoring/tutorial-access-api-with-certificates).
- Review [directoryAudit](directoryaudit.md) resource and actions. - Review [signIn](signin.md) resource and actions. <!--
v1.0 Azure Ad Overview https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/v1.0/resources/azure-ad-overview.md
Directory resources and APIs can open up new ways for you to engage with users a
- Drill down on the methods and properties of the resources most helpful to your scenario. - Try the API in the [Graph Explorer](https://developer.microsoft.com/graph/graph-explorer).
-Need more ideas? See [how some of our partners are using Microsoft Graph](https://developer.microsoft.com/graph/graph/examples#partners).
+Need more ideas? See [how some of our partners are using Microsoft Graph](https://developer.microsoft.com/graph/partners).
v1.0 Changenotification https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/v1.0/resources/changenotification.md
None.
| clientState | string | Value of the **clientState** property sent in the subscription request (if any). The maximum length is 255 characters. The client can check whether the change notification came from the service by comparing the values of the **clientState** property. The value of the **clientState** property sent with the subscription is compared with the value of the **clientState** property received with each change notification. Optional. | | encryptedContent | [changeNotificationEncryptedContent](changenotificationencryptedcontent.md) | (Preview) Encrypted content attached with the change notification. Only provided if **encryptionCertificate** and **includeResourceData** were defined during the subscription request and if the resource supports it. Optional. | | id | string | Unique ID for the notification. Optional. |
-| lifecycleEvent | lifecycleEventType| The type of lifecycle notification if the current notification is a lifecycle notification. Optional. Supported values are `missed`, `removed`, `reauthorizationRequired`. |
+| lifecycleEvent | lifecycleEventType| The type of lifecycle notification if the current notification is a lifecycle notification. Optional. Supported values are `missed`, `subscriptionRemoved`, `reauthorizationRequired`. |
| resource | string | The URI of the resource that emitted the change notification relative to `https://graph.microsoft.com`. Required. | | resourceData | [resourceData](resourcedata.md) | The content of this property depends on the type of resource being subscribed to. Required. | | subscriptionExpirationDateTime | DateTimeOffset | The expiration time for the subscription. Required. |
v1.0 Directoryrole https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/v1.0/resources/directoryrole.md
This resource supports:
|[List members](../api/directoryrole-list-members.md) |[directoryObject](directoryobject.md) collection| Get the users that are members of the directory role from the members navigation property.| |[Remove a member](../api/directoryrole-delete-member.md) |[directoryObject](directoryobject.md)| Remove a user from the directory role.| |[Activate directoryRole](../api/directoryrole-post-directoryroles.md) |[directoryRole](directoryrole.md) | Activate a directory role.|
+|[List scopedMembers](../api/directoryrole-list-scopedmembers.md) |[scopedRoleMembership](scopedrolemembership.md) collection| List the members of this directory role that are scoped to [administrative units](administrativeunit.md), through the scopedRoleMembership resource collection.|
|[delta](../api/directoryrole-delta.md)|directoryRole collection| Get incremental changes for directory roles. | ## Properties
This resource supports:
| Relationship | Type |Description| |:|:--|:-| |members|[directoryObject](directoryobject.md) collection|Users that are members of this directory role. HTTP Methods: GET, POST, DELETE. Read-only. Nullable.|
+|scopedMembers|[scopedRoleMembership](scopedrolemembership.md) collection| Members of this directory role that are scoped to [administrative units](administrativeunit.md). Read-only. Nullable.|
## JSON representation
v1.0 Mail Api Overview https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/v1.0/resources/mail-api-overview.md
The mail API can open up new ways for you to engage with users:
- Drill down on the [methods](../resources/message.md#methods), [properties](../resources/message.md#properties), and [relationships](../resources/message.md#relationships) of the [message](../resources/message.md) and [mailFolder](../resources/mailfolder.md) resources. - Try the API in the [Graph Explorer](https://developer.microsoft.com/graph/graph-explorer).
-Need more ideas? See [how some of our partners are using Microsoft Graph](https://developer.microsoft.com/graph/graph/examples#partners).
+Need more ideas? See [how some of our partners are using Microsoft Graph](https://developer.microsoft.com/graph/partners).
v1.0 Report https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/v1.0/resources/report.md
Reports resources and APIs can open up new ways for you to engage with users and
- Drill down on the methods and properties of the resources most helpful to your scenario. - Try the API in the [Graph Explorer](https://developer.microsoft.com/graph/graph-explorer).
-Need more ideas? See [how some of our partners are using Microsoft Graph](https://developer.microsoft.com/graph/graph/examples#partners).
+Need more ideas? See [how some of our partners are using Microsoft Graph](https://developer.microsoft.com/graph/partners).
v1.0 Security Api Overview https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/v1.0/resources/security-api-overview.md
The Microsoft Graph Security API can open up new ways for you to engage with dif
- Try the API in the [Graph Explorer](https://developer.microsoft.com/graph/graph-explorer). Under **Sample Queries**, choose **show more samples** and set the Security category to **on**. - Try [subscribing to and receiving notifications](/graph/webhooks) on entity changes.
-Need more ideas? See [how some of our partners are using Microsoft Graph](https://developer.microsoft.com/graph/graph/examples#partners).
+Need more ideas? See [how some of our partners are using Microsoft Graph](https://developer.microsoft.com/graph/partners).
## See also
v1.0 User https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/v1.0/resources/user.md
This resource supports:
|companyName | String | The company name which the user is associated. This property can be useful for describing the company that an external user comes from. The maximum length of the company name is 64 characters.<br><br>Returned only on `$select`. Supports `$filter` (`eq`, `ne`, `NOT`, `ge`, `le`, `in`, `startsWith`).| |consentProvidedForMinor|[consentProvidedForMinor](#consentprovidedforminor-values)|Sets whether consent has been obtained for minors. Allowed values: `null`, `granted`, `denied` and `notRequired`. Refer to the [legal age group property definitions](#legal-age-group-property-definitions) for further information. <br><br>Returned only on `$select`. Supports `$filter` (`eq`, `ne`, `NOT`, and `in`).| |country|String|The country/region in which the user is located; for example, `US` or `UK`. Maximum length is 128 characters. <br><br>Returned only on `$select`. Supports `$filter` (`eq`, `ne`, `NOT`, `ge`, `le`, `in`, `startsWith`).|
-|createdDateTime | DateTimeOffset |The created date of the user object. Read-only. <br><br>Returned only on `$select`. Supports `$filter` (`eq`, `ne`, `NOT` , `ge`, `le`, and `in` operators) and `$orderBy`.|
+|createdDateTime | DateTimeOffset |The created date of the user object. Read-only. <br><br>Returned only on `$select`. Supports `$filter` (`eq`, `ne`, `NOT` , `ge`, `le`, and `in` operators).|
|creationType|String|Indicates whether the user account was created as a regular school or work account (`null`), an external account (`Invitation`), a local account for an Azure Active Directory B2C tenant (`LocalAccount`) or self-service sign-up using email verification (`EmailVerified`). Read-only. <br><br>Returned only on `$select`. Supports `$filter` (`eq`, `ne`, `NOT`, and `in`).|
-|deletedDateTime| DateTimeOffset | The date and time the user was deleted. <br><br>Returned only on `$select`. Supports `$filter` (`eq`, `ne`, `NOT`, `ge`, `le`, and `in`) and `$orderBy`. |
+|deletedDateTime| DateTimeOffset | The date and time the user was deleted. <br><br>Returned only on `$select`. Supports `$filter` (`eq`, `ne`, `NOT`, `ge`, `le`, and `in`). |
|department|String|The name for the department in which the user works. Maximum length is 64 characters. <br><br>Returned only on `$select`. Supports `$filter` (`eq`, `ne`, `NOT` , `ge`, `le`, and `in` operators).| |displayName|String|The name displayed in the address book for the user. This is usually the combination of the user's first name, middle initial and last name. This property is required when a user is created and it cannot be cleared during updates. Maximum length is 256 characters. <br><br>Returned by default. Supports `$filter` (`eq`, `ne`, `NOT` , `ge`, `le`, `in`, `startsWith`), `$orderBy`, and `$search`.| | employeeHireDate | DateTimeOffset | The date and time when the user was hired or will start work in case of a future hire. <br><br>Returned only on `$select`. Supports `$filter` (`eq`, `ne`, `NOT` , `ge`, `le`, `in`).|
v1.0 Toc.Yml https://github.com/microsoftgraph/microsoft-graph-docs/commits/master/api-reference/v1.0/toc.yml a/api-reference/v1.0/toc.yml
items:
href: api/directoryrole-post-members.md - name: Remove member href: api/directoryrole-delete-member.md
+ - name: List scoped members
+ href: api/directoryrole-list-scopedmembers.md
+ - name: Get delta
+ href: api/directoryrole-delta.md
- name: Directory role template href: resources/directoryroletemplate.md items: