Skip to content

Commit

Permalink
Merge pull request #24394 from microsoftgraph/main
Browse files Browse the repository at this point in the history
Merge to publish.
  • Loading branch information
Lauragra authored May 25, 2024
2 parents 94091ae + 1e47c7b commit c389f58
Show file tree
Hide file tree
Showing 49 changed files with 2,019 additions and 32 deletions.
12 changes: 9 additions & 3 deletions api-reference/beta/api/user-list.md
Original file line number Diff line number Diff line change
Expand Up @@ -386,7 +386,9 @@ Content-type: application/json
"lastSignInDateTime": "2021-07-29T15:53:27Z",
"lastSignInRequestId": "f3149ee1-e347-4181-b45b-99a1f82b1c00",
"lastNonInteractiveSignInDateTime": "2021-07-29T17:53:42Z",
"lastNonInteractiveSignInRequestId": "868efa6a-b2e9-40e9-9b1c-0aaea5b50200"
"lastNonInteractiveSignInRequestId": "868efa6a-b2e9-40e9-9b1c-0aaea5b50200",
"lastSuccessfulSignInDateTime": "",
"lastSuccessfulSignInRequestId": ""
}
}
]
Expand Down Expand Up @@ -432,7 +434,9 @@ Content-type: application/json
"lastSignInDateTime": "2021-06-17T16:41:33Z",
"lastSignInRequestId": "d4d31c40-4c36-4775-ad59-7d1e6a171f00",
"lastNonInteractiveSignInDateTime": "0001-01-01T00:00:00Z",
"lastNonInteractiveSignInRequestId": ""
"lastNonInteractiveSignInRequestId": "",
"lastSuccessfulSignInDateTime": "",
"lastSuccessfulSignInRequestId": ""
}
},
{
Expand All @@ -442,7 +446,9 @@ Content-type: application/json
"lastSignInDateTime": "2021-07-29T15:53:27Z",
"lastSignInRequestId": "f3149ee1-e347-4181-b45b-99a1f82b1c00",
"lastNonInteractiveSignInDateTime": "2021-07-29T17:53:42Z",
"lastNonInteractiveSignInRequestId": "868efa6a-b2e9-40e9-9b1c-0aaea5b50200"
"lastNonInteractiveSignInRequestId": "868efa6a-b2e9-40e9-9b1c-0aaea5b50200",
"lastSuccessfulSignInDateTime": "",
"lastSuccessfulSignInRequestId": ""
}
}
]
Expand Down
6 changes: 3 additions & 3 deletions api-reference/beta/resources/groups-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,9 +32,9 @@ Microsoft Entra ID supports the following types of groups.
> [!NOTE]
> Microsoft also supports [dynamic distribution groups](/exchange/recipients/dynamic-distribution-groups/dynamic-distribution-groups?view=exchserver-2019&preserve-view=true) which can't be managed or retrieved through Microsoft Graph.
In Microsoft Graph, the type of group can be identified by the settings of its **groupType**, **mailEnabled**, and **securityEnabled** properties. The following table indicates how to differentiate the groups by their settings, and whether the group types can be managed through the Microsoft Graph groups APIs.
In Microsoft Graph, the type of group can be identified by the settings of its **groupTypes**, **mailEnabled**, and **securityEnabled** properties. The following table indicates how to differentiate the groups by their settings, and whether the group types can be managed through the Microsoft Graph groups APIs.

| Type |groupType | mailEnabled | securityEnabled | Created and managed via the groups APIs |
| Type |groupTypes | mailEnabled | securityEnabled | Created and managed via the groups APIs |
|--|--|--|--|--|
| [Microsoft 365 groups](#microsoft-365-groups) | `["Unified"]` | `true` | `true` or `false` | Yes |
| [Security groups](#security-groups-and-mail-enabled-security-groups) | `[]` | `false` | `true` | Yes |
Expand Down Expand Up @@ -142,7 +142,7 @@ The following example shows a complete rule.

You can combine multiple expressions in a rule using the `and`, `or`, and `not` operators.

The **groupType** property must also include the `"DynamicMembership"` value in the collection. The dynamic membership rule can be turned on or off through the **membershipRuleProcessingState** property. You can update a group with assigned membership to have dynamic membership.
The **groupTypes** property must also include the `"DynamicMembership"` value in the collection. The dynamic membership rule can be turned on or off through the **membershipRuleProcessingState** property. You can update a group with assigned membership to have dynamic membership.

The following example request creates a new Microsoft 365 group that can only include employees in the Marketing department.

Expand Down
16 changes: 9 additions & 7 deletions api-reference/beta/resources/signinactivity.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,12 +21,12 @@ Effective December 1, 2023, the **lastSuccessfulSignInDateTime** property is ava

| Property | Type | Description |
|:-------------|:------------|:------------|
|lastSignInDateTime|DateTimeOffset|The last interactive sign-in date and time for a specific user. You can use this field to calculate the last time a user attempted (either successfully or unsuccessfully) to sign in to the directory the directory with an interactive authentication method. This field can be used to build reports, such as inactive users. The timestamp 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'`. Microsoft Entra ID maintains interactive sign-ins going back to April 2020. For more information about using the value of this property, see [Manage inactive user accounts in Microsoft Entra ID](/azure/active-directory/reports-monitoring/howto-manage-inactive-user-accounts).|
|lastSignInRequestId|String|Request identifier of the last interactive sign-in performed by this user.|
|lastNonInteractiveSignInDateTime|DateTimeOffset|The last non-interactive sign-in date for a specific user. You can use this field to calculate the last time a client attempted (either successfully or unsuccessfully) to sign in to the directory on behalf of a user. Because some users may use clients to access tenant resources rather than signing into your tenant directly, you can use the non-interactive sign-in date to along with lastSignInDateTime to identify inactive users. The timestamp 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'`. Microsoft Entra ID maintains non-interactive sign-ins going back to May 2020. For more information about using the value of this property, see [Manage inactive user accounts in Microsoft Entra ID](/azure/active-directory/reports-monitoring/howto-manage-inactive-user-accounts).|
|lastNonInteractiveSignInDateTime|DateTimeOffset|The last non-interactive sign-in date for a specific user. You can use this field to calculate the last time a client attempted (either successfully or unsuccessfully) to sign in to the directory on behalf of a user. Because some users may use clients to access tenant resources rather than signing into your tenant directly, you can use the non-interactive sign-in date to along with lastSignInDateTime to identify inactive users. The timestamp type represents date and time information using ISO 8601 format and is always in UTC. For example, midnight UTC on Jan 1, 2014 is `2014-01-01T00:00:00Z`. Microsoft Entra ID maintains non-interactive sign-ins going back to May 2020. For more information about using the value of this property, see [Manage inactive user accounts in Microsoft Entra ID](/azure/active-directory/reports-monitoring/howto-manage-inactive-user-accounts).|
|lastNonInteractiveSignInRequestId|String|Request identifier of the last non-interactive sign-in performed by this user.|
|lastSuccessfulSignInDateTime|DateTimeOffset|The datetime of the user's most recent successful sign in activity.|
|lastSuccessfulSignInRequestId|String|The requestID of the last successful signIn.|
|lastSignInDateTime|DateTimeOffset|The last interactive sign-in date and time for a specific user. You can use this field to calculate the last time a user attempted (either successfully or unsuccessfully) to sign in to the directory the directory with an interactive authentication method. This field can be used to build reports, such as inactive users. The timestamp type represents date and time information using ISO 8601 format and is always in UTC. For example, midnight UTC on Jan 1, 2014 is `2014-01-01T00:00:00Z`. Microsoft Entra ID maintains interactive sign-ins going back to April 2020. For more information about using the value of this property, see [Manage inactive user accounts in Microsoft Entra ID](/azure/active-directory/reports-monitoring/howto-manage-inactive-user-accounts).|
|lastSignInRequestId|String|Request identifier of the last interactive sign-in performed by this user.|
|lastSuccessfulSignInDateTime|DateTimeOffset|The date and time of the user's most recent successful sign-in activity. The timestamp type represents date and time information using ISO 8601 format and is always in UTC. For example, midnight UTC on Jan 1, 2014 is `2014-01-01T00:00:00Z`.|
|lastSuccessfulSignInRequestId|String|The request ID of the last successful sign-in.|

## JSON representation

Expand All @@ -44,10 +44,12 @@ The following is a JSON representation of the resource.
```json
{
"@odata.type": "#microsoft.graph.signInActivity",
"lastNonInteractiveSignInDateTime": "String (timestamp)",
"lastNonInteractiveSignInRequestId": "String",
"lastSignInDateTime": "String (timestamp)",
"lastSignInRequestId": "String",
"lastNonInteractiveSignInDateTime": "String (timestamp)",
"lastNonInteractiveSignInRequestId": "String"
"lastSuccessfulSignInDateTime": "String (timestamp)",
"lastSuccessfulSignInRequestId": "String"
}
```

Expand Down
76 changes: 76 additions & 0 deletions api-reference/v1.0/api/filestorage-delete-containers.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,76 @@
---
title: "Delete fileStorageContainer"
description: "Delete a fileStorageContainer object."
author: "tonchan-msft"
ms.localizationpriority: medium
ms.subservice: "onedrive"
doc_type: apiPageType
---

# Delete fileStorageContainer

Namespace: microsoft.graph

Delete a [fileStorageContainer](../resources/filestoragecontainer.md) object. This method moves the **fileStorageContainer** to the recycle bin, instead of permanently deleting it.

## Permissions

Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions [only if your app requires it](/graph/permissions-overview#best-practices-for-using-microsoft-graph-permissions). For details about delegated and application permissions, see [Permission types](/graph/permissions-overview#permission-types). To learn more about these permissions, see the [permissions reference](/graph/permissions-reference).


<!-- { "blockType": "permissions", "name": "filestorage_delete_containers" } -->
[!INCLUDE [permissions-table](../includes/permissions/filestorage-delete-containers-permissions.md)]

[!INCLUDE [app-permissions](../includes/sharepoint-embedded-app-permissions.md)]

## HTTP request

<!-- {
"blockType": "ignored"
}
-->
``` http
DELETE /storage/fileStorage/containers/{containerId}
```

## Request headers

|Name|Description|
|:---|:---|
|Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|

## Request body

Don't supply a request body for this method.

## Response

If successful, this method returns a `204 No Content` response code.

## Examples

### Request

The following example shows a request.
<!-- {
"blockType": "request",
"name": "delete_filestoragecontainer"
}
-->
``` http
DELETE https://graph.microsoft.com/v1.0/storage/fileStorage/containers/b!ISJs1WRro0y0EWgkUYcktDa0mE8zSlFEqFzqRn70Zwp1CEtDEBZgQICPkRbil_5Z
```


### Response

The following example shows the response.
<!-- {
"blockType": "response",
"truncated": true
}
-->
``` http
HTTP/1.1 204 No Content
```

98 changes: 98 additions & 0 deletions api-reference/v1.0/api/filestorage-list-containers.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,98 @@
---
title: "List containers"
description: "Get a list of fileStorageContainers and their properties."
author: "tonchan-msft"
ms.localizationpriority: medium
ms.subservice: "onedrive"
doc_type: apiPageType
---

# List containers


Namespace: microsoft.graph

Retrieve a list of [fileStorageContainer](../resources/filestoragecontainer.md) objects that are visible to the caller. The `containerTypeId` filter parameter is required.

## Permissions

Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions [only if your app requires it](/graph/permissions-overview#best-practices-for-using-microsoft-graph-permissions). For details about delegated and application permissions, see [Permission types](/graph/permissions-overview#permission-types). To learn more about these permissions, see the [permissions reference](/graph/permissions-reference).

<!-- { "blockType": "permissions", "name": "filestorage_list_containers" } -->
[!INCLUDE [permissions-table](../includes/permissions/filestorage-list-containers-permissions.md)]

[!INCLUDE [app-permissions](../includes/sharepoint-embedded-app-permissions.md)]

## HTTP request

<!-- {
"blockType": "ignored"
}
-->
``` http
GET /storage/fileStorage/containers?$filter=containerTypeId eq {containerTypeId}
GET /storage/fileStorage/containers?$filter=containerTypeId eq {containerTypeId} and viewpoint/effectiveRole eq 'principalOwner'
```

## Query parameters

This method required the `containerTypeId` parameter. It supports the `$expand` OData query parameter, except for the **drive**, **permissions**, and **customProperties** properties. For more information, see [OData query parameters](/graph/query-parameters).

## Request headers

|Name|Description|
|:---|:---|
|Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|

## Request body

Don't supply a request body for this method.

## Response

If successful, this method returns a `200 OK` response code and a collection of [fileStorageContainer](../resources/filestoragecontainer.md) objects in the response body. Only a limited subset of properties is returned for each **fileStorageContainer**.

## Examples

### Request

The following example enumerates all containers of a given container type.


<!-- {
"blockType": "request",
"name": "list_filestoragecontainer"
}
-->
``` http
GET https://graph.microsoft.com/v1.0/storage/fileStorage/containers?$filter=containerTypeId eq e2756c4d-fa33-4452-9c36-2325686e1082
```

### Response

The following example shows the response.
<!-- {
"blockType": "response",
"truncated": true,
"@odata.type": "Collection(microsoft.graph.fileStorageContainer)"
}
-->
``` http
HTTP/1.1 200 OK
Content-Type: application/json
{
"@odata.context": "https://graph.microsoft.com/v1.0/storage/fileStorage/containers",
"@odata.count": 1,
"value": [
{
"@odata.type": "#microsoft.graph.fileStorageContainer",
"id": "b!ISJs1WRro0y0EWgkUYcktDa0mE8zSlFEqFzqRn70Zwp1CEtDEBZgQICPkRbil_5Z",
"displayName": "My File Storage Container",
"containerTypeId": "e2756c4d-fa33-4452-9c36-2325686e1082",
"createdDateTime": "2021-11-24T15:41:52.347Z"
}
]
}
```

82 changes: 82 additions & 0 deletions api-reference/v1.0/api/filestoragecontainer-activate.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,82 @@
---
title: "fileStorageContainer: activate"
description: "Activate a fileStorageContainer object."
author: "tonchan-msft"
ms.localizationpriority: medium
ms.subservice: "onedrive"
doc_type: apiPageType
---

# fileStorageContainer: activate

Namespace: microsoft.graph

Activate a [fileStorageContainer](../resources/filestoragecontainer.md) object.

A **fileStorageContainer** object is created in an inactive state, as indicated by the **status** property. A container must be activated within 24 hours after creation, or it will be automatically deleted. Upon activation, the value of the status property changes from `inactive` to `active`.

A **fileStorageContainer** can be activated by calling the **activate** API, or any other API that updates or modifies the **fileStorageContainer** or its content. For example, uploading a file to a **fileStorageContainer**, adding permission to a **fileStorageContainer**, creating a custom property on a **fileStorageContainer**, or updating the properties of a **fileStorageContainer** can activate it.


## Permissions

Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions [only if your app requires it](/graph/permissions-overview#best-practices-for-using-microsoft-graph-permissions). For details about delegated and application permissions, see [Permission types](/graph/permissions-overview#permission-types). To learn more about these permissions, see the [permissions reference](/graph/permissions-reference).


<!-- { "blockType": "permissions", "name": "filestoragecontainer_activate" } -->
[!INCLUDE [permissions-table](../includes/permissions/filestoragecontainer-activate-permissions.md)]

[!INCLUDE [app-permissions](../includes/sharepoint-embedded-app-permissions.md)]

## HTTP request

<!-- {
"blockType": "ignored"
}
-->
``` http
POST /storage/fileStorage/containers/{containerId}/activate
```

## Request headers

|Name|Description|
|:---|:---|
|Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|

## Request body

Don't supply a request body for this method.

## Response

If successful, this action returns a `204 No Content` response code.

## Examples

### Request

The following example shows a request.

<!-- {
"blockType": "request",
"name": "activate_filestoragecontainer"
}
-->
``` http
POST https://graph.microsoft.com/v1.0/storage/fileStorage/containers/b!ISJs1WRro0y0EWgkUYcktDa0mE8zSlFEqFzqRn70Zwp1CEtDEBZgQICPkRbil_5Z/activate
```

### Response

The following example shows the response.

<!-- {
"blockType": "response",
"truncated": true
}
-->
``` http
HTTP/1.1 204 No Content
```

Loading

0 comments on commit c389f58

Please sign in to comment.