Skip to content

Commit ca0d03b

Browse files
DanielabomDanielabom
authored
Merge branch 'main' into neelporiya/add-site-archive-unarchive-api-docs
2 parents fff9d8a + 2319fab commit ca0d03b

File tree

145 files changed

+3267
-597
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

145 files changed

+3267
-597
lines changed

‎api-reference/beta/api/certificateauthoritypath-list-mutualtlsoauthconfigurations.md

Lines changed: 107 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,107 @@
1+
---
2+
title: "List mutualTlsOauthConfigurations"
3+
description: "Get a list of the available mutualTlsOauthConfiguration resources."
4+
author: "sofia-geislinger"
5+
ms.date: 12/31/2024
6+
ms.localizationpriority: medium
7+
ms.subservice: "entra-id"
8+
doc_type: apiPageType
9+
---
10+
11+
# List mutualTlsOauthConfigurations
12+
13+
Namespace: microsoft.graph
14+
15+
[!INCLUDE [beta-disclaimer](../../includes/beta-disclaimer.md)]
16+
17+
Get a list of the available [mutualTlsOauthConfiguration](../resources/mutualtlsoauthconfiguration.md) resources.
18+
19+
## Permissions
20+
21+
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).
22+
23+
<!-- {
24+
"blockType": "permissions",
25+
"name": "certificateauthoritypath-list-mutualtlsoauthconfigurations-permissions"
26+
}
27+
-->
28+
[!INCLUDE [permissions-table](../includes/permissions/certificateauthoritypath-list-mutualtlsoauthconfigurations-permissions.md)]
29+
30+
[!INCLUDE [rbac-mtlsoauthconfig-apis](../includes/rbac-for-apis/rbac-mtlsoauthconfig-apis.md)]
31+
32+
## HTTP request
33+
34+
<!-- {
35+
"blockType": "ignored"
36+
}
37+
-->
38+
``` http
39+
GET /certificateAuthorities/mutualTlsOauthConfigurations
40+
```
41+
42+
## Optional query parameters
43+
44+
This method supports the `$count`, `$filter`, and `$select` OData query parameters to help customize the response. For general information, see [OData query parameters](/graph/query-parameters).
45+
46+
## Request headers
47+
48+
|Name|Description|
49+
|:---|:---|
50+
|Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|
51+
52+
## Request body
53+
54+
Don't supply a request body for this method.
55+
56+
## Response
57+
58+
If successful, this method returns a `200 OK` response code and a collection of [mutualTlsOauthConfiguration](../resources/mutualtlsoauthconfiguration.md) objects in the response body.
59+
60+
For more information, see [Microsoft Graph error responses and resource types](/graph/errors).
61+
62+
## Examples
63+
64+
### Request
65+
66+
The following example shows a request.
67+
<!-- {
68+
"blockType": "request",
69+
"name": "certificateauthoritypath-list-mutualtlsoauthconfigurations-permissions"
70+
}
71+
-->
72+
73+
```http
74+
GET https://graph.microsoft.com/beta/directory/certificateAuthorities/mutualTlsOauthConfigurations
75+
```
76+
77+
### Response
78+
79+
The following example shows the response.
80+
>**Note:** The response object shown here might be shortened for readability.
81+
<!-- {
82+
"blockType": "response",
83+
"truncated": true,
84+
"@odata.type": "Collection(microsoft.graph.mutualTlsOauthConfiguration)"
85+
}
86+
-->
87+
``` http
88+
HTTP/1.1 200 OK
89+
Content-Type: application/json
90+
91+
{
92+
"@odata.context": "https://graph.microsoft.com/beta/$metadata#directory/certificateAuthorities/mutualTlsOauthConfigurations",
93+
"value": [
94+
{
95+
"id": "a7199212-950f-4a2d-ba1e-017c48da1d19",
96+
"deletedDateTime": null,
97+
"displayName": "Standard TLS cert config",
98+
"tlsClientAuthParameter": "tls_client_auth_san_uri",
99+
"certificateAuthorities": [
100+
{
101+
"@odata.type": "microsoft.graph.certificateAuthority"
102+
}
103+
]
104+
}
105+
]
106+
}
107+
```

‎api-reference/beta/api/certificateauthoritypath-post-mutualtlsoauthconfigurations.md

Lines changed: 116 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,116 @@
1+
---
2+
title: "Create mutualTlsOauthConfiguration"
3+
description: "Create a mutualTlsOauthConfiguration resource that contains a specified certificate authority object."
4+
author: "sofia-geislinger"
5+
ms.date: 12/31/2024
6+
ms.localizationpriority: medium
7+
ms.subservice: "entra-id"
8+
doc_type: apiPageType
9+
---
10+
11+
# Create mutualTlsOauthConfiguration
12+
13+
Namespace: microsoft.graph
14+
15+
[!INCLUDE [beta-disclaimer](../../includes/beta-disclaimer.md)]
16+
17+
Create a [mutualTlsOauthConfiguration](../resources/mutualtlsoauthconfiguration.md) resource that contains a specified certificate authority object.
18+
19+
## Permissions
20+
21+
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).
22+
23+
<!-- { "blockType": "permissions", "name": "certificateauthoritypath_post_mutualtlsoauthconfigurations" } -->
24+
[!INCLUDE [permissions-table](../includes/permissions/certificateauthoritypath-post-mutualtlsoauthconfigurations-permissions.md)]
25+
26+
[!INCLUDE [rbac-mtlsoauthconfig-apis](../includes/rbac-for-apis/rbac-mtlsoauthconfig-apis.md)]
27+
28+
## HTTP request
29+
30+
<!-- {
31+
"blockType": "ignored"
32+
}
33+
-->
34+
35+
``` http
36+
POST /directory/certificateAuthorities/mutualTlsOauthConfigurations
37+
```
38+
39+
## Request headers
40+
41+
|Name|Description|
42+
|:---|:---|
43+
|Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|
44+
|Content-Type|application/json. Required.|
45+
46+
## Request body
47+
48+
In the request body, supply a JSON representation of the [mutualTlsOauthConfiguration](../resources/mutualtlsoauthconfiguration.md) object.
49+
50+
You can specify the following properties when you create a **mutualTlsOauthConfiguration**.
51+
52+
|Property|Type|Description|
53+
|:---|:---|:---|
54+
|certificateAuthority|[certificateAuthority](../resources/certificateauthority.md) collection | Multi-value property that represents a list of trusted certificate authorities. Optional. |
55+
|displayName|String|Friendly name. Optional. |
56+
|tlsClientAuthParameter| tlsClientRegistrationMetadata | Specifies which field in the certificate contains the subject ID. The possible values are: `tls_client_auth_subject_dn`, `tls_client_auth_san_dns`, `tls_client_auth_san_uri`, `tls_client_auth_san_ip`, `tls_client_auth_san_email`, `unknownFutureValue`. Required. Read-only. |
57+
58+
## Response
59+
60+
If successful, this method returns a `201 Created` response code and a [mutualTlsOauthConfiguration](../resources/mutualtlsoauthconfiguration.md) object in the response body. If a validation failure occurs during the certificate validation steps, the method returns a `400 Bad Request` along with the error message, `Invalid value specified for property 'certificate' of resource 'CertificateAuthorityInformation'.`.
61+
62+
For more information, see [Microsoft Graph error responses and resource types](/graph/errors).
63+
64+
## Examples
65+
66+
### Request
67+
68+
The following example shows a request.
69+
<!-- {
70+
"blockType": "request",
71+
"name": "create_mutualtlsoauthconfiguration_from_"
72+
}
73+
-->
74+
75+
```http
76+
POST https://graph.microsoft.com/beta/directory/certificateAuthorities/mutualTlsOauthConfigurations
77+
Content-Type: application/json
78+
79+
{
80+
"displayName": "DoorCamera_Model_X_TrustedCAs",
81+
"tlsClientAuthParameter": "tls_client_auth_san_uri",
82+
"certificateAuthorities": [
83+
{
84+
"@odata.type": "microsoft.graph.certificateAuthority"
85+
}
86+
]
87+
}
88+
```
89+
90+
91+
### Response
92+
93+
The following example shows the response.
94+
>**Note:** The response object shown here might be shortened for readability.
95+
<!-- {
96+
"blockType": "response",
97+
"truncated": true,
98+
"@odata.type": "microsoft.graph.mutualTlsOauthConfiguration"
99+
}
100+
-->
101+
``` http
102+
HTTP/1.1 201 Created
103+
Content-Type: application/json
104+
105+
{
106+
"@odata.context": "https://graph.microsoft.com/beta/$metadata#directory/certificateAuthorities/mutualTlsOauthConfigurations/$entity",
107+
"id":"eec5ba11-2fc0-4113-83a2-ed986ed13cdb",
108+
"displayName": "DoorCamera_Model_X_TrustedCAs",
109+
"tlsClientAuthParameter": "tls_client_auth_san_uri",
110+
"certificateAuthorities": [
111+
{
112+
"@odata.type": "microsoft.graph.certificateAuthority"
113+
}
114+
]
115+
}
116+
```

‎api-reference/beta/api/cloudpcbulkaction-retry.md

Lines changed: 95 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,95 @@
1+
---
2+
title: "cloudPcBulkAction: retry"
3+
description: "Retry a cloudPcBulkAction object with selected Cloud PCs."
4+
author: "AshleyYangSZ"
5+
ms.localizationpriority: medium
6+
ms.subservice: "cloud-pc"
7+
doc_type: apiPageType
8+
ms.date: 01/01/2025
9+
---
10+
11+
# cloudPcBulkAction: retry
12+
13+
Namespace: microsoft.graph
14+
15+
[!INCLUDE [beta-disclaimer](../../includes/beta-disclaimer.md)]
16+
17+
Retry a [cloudPcBulkAction](../resources/cloudpcbulkaction.md) object with selected Cloud PCs.
18+
19+
[!INCLUDE [national-cloud-support](../../includes/global-us.md)]
20+
21+
## Permissions
22+
23+
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).
24+
25+
<!-- { "blockType": "permissions", "name": "cloudpcbulkaction_retry" } -->
26+
[!INCLUDE [permissions-table](../includes/permissions/cloudpcbulkaction-retry-permissions.md)]
27+
28+
## HTTP request
29+
30+
<!-- {
31+
"blockType": "ignored"
32+
}
33+
-->
34+
35+
``` http
36+
POST /deviceManagement/virtualEndpoint/bulkAction/{id}/retry
37+
```
38+
39+
## Request headers
40+
41+
|Name|Description|
42+
|:---|:---|
43+
|Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|
44+
|Content-Type|application/json. Required.|
45+
46+
## Request body
47+
48+
In the request body, supply a JSON representation of the parameters.
49+
50+
The following table shows the parameters that can be used with this method.
51+
52+
|Property|Type|Description|
53+
|:---|:---|:---|
54+
|cloudPcIds|String collection|A list of IDs for the Cloud PC devices to be retried for the given bulk action. This is optional; if not provided, all failed devices are retried.|
55+
56+
## Response
57+
58+
If successful, this method returns a `202 Accepted` response code.
59+
60+
## Examples
61+
62+
### Request
63+
64+
The following example shows a request.
65+
66+
<!-- {
67+
"blockType": "request",
68+
"name": "cloudpcbulkaction_retry"
69+
}
70+
-->
71+
``` http
72+
POST https://graph.microsoft.com/beta/deviceManagement/virtualEndpoint/bulkAction/0d76d02b-e0a0-4f58-baff-d1718cc2d144/retry
73+
Content-Type: application/json
74+
75+
{
76+
"@odata.type": "#microsoft.graph.cloudPcBulkAction",
77+
"cloudPcIds": [
78+
"30d0e128-de93-41dc-89ec-33d84bb662a0",
79+
"7c82a3e3-9459-44e4-94d9-b92f93bf78dd"
80+
]
81+
}
82+
```
83+
84+
### Response
85+
86+
The following example shows the response.
87+
88+
<!-- {
89+
"blockType": "response",
90+
"truncated": true
91+
}
92+
-->
93+
``` http
94+
HTTP/1.1 202 Accepted
95+
```

‎api-reference/beta/api/corsconfiguration_v2-get.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,6 @@ GET https://graph.microsoft.com/beta/applications/{applicationObjectId}/onPremis
7878

7979
---
8080

81-
8281
### Response
8382

8483
The following example shows the response.

‎api-reference/beta/api/corsconfiguration_v2-update.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,6 @@ Content-Type: application/json
9797

9898
---
9999

100-
101100
### Response
102101

103102
The following example shows the response.

‎api-reference/beta/api/device-update.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: "sandeo-MSFT"
55
ms.localizationpriority: medium
66
ms.subservice: "entra-directory-management"
77
doc_type: apiPageType
8-
ms.date: 10/25/2024
8+
ms.date: 12/31/2024
99
---
1010

1111
# Update device
@@ -50,11 +50,12 @@ In the request body, supply the values for the [device](../resources/device.md)
5050
| Property | Type |Description|
5151
|:---------------|:--------|:----------|
5252
|accountEnabled|Boolean| `true` if the account is enabled; otherwise, `false`. Only callers with at least the *Cloud Device Administrator* role can update this property. |
53-
|operatingSystem|String|The type of operating system on the device.|
54-
|operatingSystemVersion|String|The version of the operating system on the device|
53+
|alternativeNames|String collection|List of alternative names for the device, for example, `resourceIds`.|
5554
|displayName|String|The display name for the device.|
5655
|isCompliant|Boolean|`true` if the device complies with Mobile Device Management (MDM) policies; otherwise, `false`. This can only be updated by Intune for any device OS type or by an [approved MDM app](/windows/client-management/mdm/azure-active-directory-integration-with-mdm) for Windows OS devices. |
5756
|isManaged|Boolean|`true` if the device is managed by a Mobile Device Management (MDM) app; otherwise, `false`. This can only be updated by Intune for any device OS type or by an [approved MDM app](/windows/client-management/mdm/azure-active-directory-integration-with-mdm) for Windows OS devices. |
57+
|operatingSystem|String|The type of operating system on the device.|
58+
|operatingSystemVersion|String|The version of the operating system on the device.|
5859

5960
Since the **device** resource supports [extensions](/graph/extensibility-overview), you can use the `PATCH` operation to
6061
add, update, or delete your own app-specific data in custom properties of an extension in an existing **device** instance.

0 commit comments

Comments
 (0)