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/cloudpcdeviceimage-getsourceimages.md
+69-4Lines changed: 69 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,6 +36,10 @@ Choose the permission or permissions marked as least privileged for this API. Us
36
36
GET /deviceManagement/virtualEndpoint/deviceImages/getSourceImages
37
37
```
38
38
39
+
## Optional query parameters
40
+
41
+
This method supports the `$filter` OData query parameter to help customize the response. For general information, see [OData query parameters](/graph/query-parameters).
42
+
39
43
## Request headers
40
44
41
45
|Name|Description|
@@ -48,11 +52,15 @@ Don't supply a request body for this method.
48
52
49
53
## Response
50
54
51
-
If successful, this function returns a `200 OK` response code and a [cloudPcSourceDeviceImage](../resources/cloudpcsourcedeviceimage.md)collection in the response body.
55
+
If successful, this function returns a `200 OK` response code and a collection of [cloudPcSourceDeviceImage](../resources/cloudpcsourcedeviceimage.md)objects in the response body.
52
56
53
57
## Examples
54
58
55
-
### Request
59
+
### Example 1: Get cloudPcSourceDeviceImage objects without any query parameters
60
+
61
+
The following example shows how to get **cloudPcSourceDeviceImage** objects without any query parameters.
62
+
63
+
#### Request
56
64
57
65
The following example shows a request.
58
66
@@ -93,7 +101,63 @@ GET https://graph.microsoft.com/beta/deviceManagement/virtualEndpoint/deviceImag
93
101
94
102
---
95
103
96
-
### Response
104
+
#### Response
105
+
106
+
The following example shows the response.
107
+
108
+
>**Note:** The response object shown here might be shortened for readability.
|groupBy|String collection|Specifies how to group the reports. If used, must have the same content as the **select** parameter.|
58
58
|orderBy|String collection|Specifies how to sort the reports.|
59
-
|reportName|[cloudPcReportName](../resources/cloudpcexportjob.md#cloudpcreportname-values)|Specifies the report name. Supports a subset of the values for **cloudPcReportName**. Supported values are: `cloudPcUsageCategoryReports`.|
59
+
|reportName|[cloudPcReportName](../resources/cloudpcreportname.md)|Specifies the report name. Supports only `cloudPcUsageCategoryReports`for **cloudPcReportName**.|
60
60
|search|String|Specifies a String to search.|
61
61
|select|String collection|OData `$select` syntax. The selected columns of the reports. |
Copy file name to clipboardExpand all lines: api-reference/beta/api/exchangemessagetrace-getdetailsbyrecipient.md
+1-5Lines changed: 1 addition & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,11 +20,7 @@ Get a list of [exchangeMessageTraceDetail](../resources/exchangemessagetracedeta
20
20
21
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).
For an app create a group with owners or members while it has the *Group.Create* permission, the app must have the privileges to read the object type that it wants to assign as the group owner or member. Therefore:
36
+
For an app to create a group with owners or members while it has the *Group.Create* permission, the app must have the privileges to read the object type that it wants to assign as the group owner or member. Therefore:
37
37
+ The app can assign itself as the group's owner or member.
38
38
+ To create the group with users as owners or members, the app must have at least the *User.Read.All* permission.
39
39
+ To create the group with other service principals as owners or members, the app must have at least the *Application.Read.All* permission.
@@ -63,7 +63,7 @@ The following table lists the properties that are required when you create the [
| displayName | string | The name to display in the address book for the group. Maximum length is 256 characters. Required. |
65
65
| mailEnabled | Boolean | Set to `true` for mail-enabled groups. Required. |
66
-
| mailNickname | string | The mail alias for the group, unique for Microsoft 365 groups in the organization. Maximum length is 64 characters. This property can contain only characters in the [ASCII character set 0 - 127](/office/vba/language/reference/user-interface-help/character-set-0127) except the following: ` @ () \ [] " ; : <> , SPACE`. Required. |
66
+
| mailNickname | string | The mail alias for the group, unique for Microsoft 365 groups in the organization. Maximum length is 64 characters. This property can contain only characters in the [ASCII character set 0 - 127](/office/vba/language/reference/user-interface-help/character-set-0127) except the following characters: ` @ () \ [] " ; : <> , SPACE`. Required. |
67
67
| securityEnabled | Boolean | Set to `true` for security-enabled groups, including Microsoft 365 groups. Required. **Note:** Groups created using the Microsoft Entra admin center or the Azure portal always have **securityEnabled** initially set to `true`. |
68
68
69
69
> [!IMPORTANT]
@@ -76,7 +76,7 @@ The following table lists the properties that are required when you create the [
76
76
>
77
77
> - A non-admin user can't add themselves to the group owners collection. For more information, see the related [known issue](https://developer.microsoft.com/en-us/graph/known-issues/?search=26419).
78
78
>
79
-
> -To following properties can't be set in the initial POST request and must be set in a subsequent PATCH request: **allowExternalSenders**, **autoSubscribeNewMembers**, **hideFromAddressLists**, **hideFromOutlookClients**, **isSubscribedByMail**, **unseenCount**.
79
+
> -The following properties can't be set in the initial POST request and must be set in a subsequent PATCH request: **allowExternalSenders**, **autoSubscribeNewMembers**, **hideFromAddressLists**, **hideFromOutlookClients**, **welcomeMessageEnabled**, **isSubscribedByMail**, **unseenCount**.
80
80
81
81
Because the **group** resource supports [extensions](/graph/extensibility-overview), you can add custom properties with your own data to the group while creating it.
82
82
@@ -97,7 +97,7 @@ If successful, this method returns a `201 Created` response code and a [group](.
97
97
98
98
### Example 1: Create a Microsoft 365 group
99
99
100
-
The following example creates a Microsoft 365 group. Because the owners have not been specified, the calling user is automatically added as the owner of the group.
100
+
The following example creates a Microsoft 365 group. When owners are not specified, the calling user is automatically added as the owner of the group.
### Example 2: Create a security group with an owner and members
214
214
215
-
The following example creates a security group with an owner and members specified. Note that a maximum of 20 relationships, such as owners and members, can be added as part of group creation. You can subsequently add more members by using the [add member](/graph/api/group-post-members?view=graph-rest-beta&preserve-view=true) API or JSON batching.
215
+
The following example creates a security group with an owner and members specified. Note that a maximum of 20 relationships, such as owners and members, can be added as part of group creation. You can then add more members by using the [add member](/graph/api/group-post-members?view=graph-rest-beta&preserve-view=true) API or JSON batching.
216
216
217
217
A non-admin user can't add themselves to the group owners collection. For more information, see the related [known issue](https://developer.microsoft.com/en-us/graph/known-issues/?search=26419).
The following is an example of a successful response. It includes only default properties. You can subsequently get the **owners** or **members** navigation properties of the group to verify the owner or members. The value of the **preferredDataLocation** property is inherited from the group creator's preferred data location.
284
+
The following example shows a successful response. It includes only default properties. You can then get the **owners** or **members** navigation properties of the group to verify the owner or members. The value of the **preferredDataLocation** property is inherited from the group creator's preferred data location.
285
285
286
286
> **Note:** The response object shown here might be shortened for readability.
Copy file name to clipboardExpand all lines: api-reference/beta/api/group-update.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,10 +58,11 @@ The following table specifies the properties that can be updated.
58
58
| securityEnabled | Boolean | Specifies whether the group is a security group, including Microsoft 365 groups. |
59
59
| uniqueName | String | The unique identifier that can be assigned to a group and used as an alternate key. Can updated only if `null` and is immutable once set. |
60
60
| visibility | String | Specifies the visibility of a Microsoft 365 group. The possible values are: **Private**, **Public**, or empty (which is interpreted as **Public**). |
61
+
| welcomeMessageEnabled | Boolean | Default is `true`. Indicates whether a welcome message is sent to new members when they are added to the Microsoft 365 group. |
61
62
| writebackConfiguration |[groupWritebackConfiguration](../resources/groupwritebackconfiguration.md)| Specifies whether or not a group is configured to write back group object properties to on-premise Active Directory. These properties are used when group writeback is configured in the [Microsoft Entra Connect](/azure/active-directory/hybrid/how-to-connect-group-writeback-v2) sync client.|
62
63
63
64
> [!IMPORTANT]
64
-
> - To update these properties (**allowExternalSenders**, **autoSubscribeNewMembers**, **hideFromAddressLists**, **hideFromOutlookClients**, **isSubscribedByMail**, **unseenCount**), you must:
65
+
> - To update these properties (**allowExternalSenders**, **autoSubscribeNewMembers**, **hideFromAddressLists**, **hideFromOutlookClients**, **isSubscribedByMail**, **unseenCount**, **welcomeMessageEnabled**), you must:
65
66
> - Specify them in their own PATCH request without including other properties from the previous table
66
67
> - Have the Group.ReadWrite.All permission (*Directory.ReadWrite.All* is not supported for these properties)
67
68
> - Only a subset of the group API that pertains to core group administration and management supports application and delegated permissions. All other members of the group API, including updating **autoSubscribeNewMembers**, support only delegated permissions.
@@ -78,7 +79,7 @@ Use this API to manage the [directory, schema, and open extensions](/graph/exten
78
79
79
80
## Response
80
81
81
-
If successful, this method returns a `204 No Content` response code—except a `200 OK` response code when updating the following properties: **allowExternalSenders**, **autoSubscribeNewMembers**, **hideFromAddressLists**, **hideFromOutlookClients**, **isSubscribedByMail**, **unseenCount**.
82
+
If successful, this method returns a `204 No Content` response code—except a `200 OK` response code when updating the following properties: **allowExternalSenders**, **autoSubscribeNewMembers**, **hideFromAddressLists**, **hideFromOutlookClients**, **isSubscribedByMail**, **unseenCount**, **welcomeMessageEnabled**.
0 commit comments