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
{{ message }}
Repository navigation
Commit 628589a
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: src/main/java/com/microsoft/graph/beta/generated/admin/windows/updates/resourceconnections/item/ResourceConnectionItemRequestBuilder.java
+13-13Lines changed: 13 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -37,18 +37,18 @@ public ResourceConnectionItemRequestBuilder(@jakarta.annotation.Nonnull final St
* @throws ODataError When receiving a 4XX or 5XX status code
42
-
* @see <a href="https://learn.microsoft.com/graph/api/windowsupdates-operationalinsightsconnection-delete?view=graph-rest-beta">Find more info here</a>
42
+
* @see <a href="https://learn.microsoft.com/graph/api/windowsupdates-resourceconnection-delete?view=graph-rest-beta">Find more info here</a>
43
43
*/
44
44
publicvoiddelete() {
45
45
delete(null);
46
46
}
47
47
/**
48
-
* Delete an operationalInsightsConnection object.
48
+
* Delete a resourceConnection object.
49
49
* @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
50
50
* @throws ODataError When receiving a 4XX or 5XX status code
51
-
* @see <a href="https://learn.microsoft.com/graph/api/windowsupdates-operationalinsightsconnection-delete?view=graph-rest-beta">Find more info here</a>
51
+
* @see <a href="https://learn.microsoft.com/graph/api/windowsupdates-resourceconnection-delete?view=graph-rest-beta">Find more info here</a>
Copy file name to clipboardExpand all lines: src/main/java/com/microsoft/graph/beta/generated/admin/windows/updates/updatableassets/item/UpdatableAssetItemRequestBuilder.java
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -93,21 +93,21 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume
Copy file name to clipboardExpand all lines: src/main/java/com/microsoft/graph/beta/generated/admin/windows/updates/updatepolicies/item/compliancechanges/item/ComplianceChangeItemRequestBuilder.java
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -46,18 +46,18 @@ public ComplianceChangeItemRequestBuilder(@jakarta.annotation.Nonnull final Stri
Copy file name to clipboardExpand all lines: src/main/java/com/microsoft/graph/beta/generated/administrativeunits/validateproperties/ValidatePropertiesRequestBuilder.java
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ public ValidatePropertiesRequestBuilder(@jakarta.annotation.Nonnull final String
* Validate that a Microsoft 365 group's display name or mail nickname complies with naming policies. Clients can use this API to determine whether a display name or mail nickname is valid before trying to create a Microsoft 365 group. For validating properties of an existing group, use the validateProperties function for groups. The following validations are performed for the display name and mail nickname properties:1. Validate the prefix and suffix naming policy2. Validate the custom banned words policy3. Validate the mail nickname is unique This API returns with the first failure encountered. If one or more properties fail multiple validations, only the property with the first validation failure is returned. However, you can validate both the mail nickname and the display name and receive a collection of validation errors if you're only validating the prefix and suffix naming policy.
38
+
* Validate that a Microsoft 365 group's display name or mail nickname complies with naming policies. Clients can use this API to determine whether a display name or mail nickname is valid before trying to create a Microsoft 365 group. For validating properties of an existing group, use the validateProperties function for groups. The following validations are performed for the display name and mail nickname properties:1. Validate the prefix and suffix naming policy2. Validate the custom banned words policy3. Validate the mail nickname is unique This API returns with the first failure encountered. If one or more properties fail multiple validations, only the property with the first validation failure is returned. However, you can validate both the mail nickname and the display name and receive a collection of validation errors if you're only validating the prefix and suffix naming policy.
39
39
* @param body The request body
40
40
* @throws ODataError When receiving a 4XX or 5XX status code
41
41
* @see <a href="https://learn.microsoft.com/graph/api/directoryobject-validateproperties?view=graph-rest-beta">Find more info here</a>
@@ -44,7 +44,7 @@ public void post(@jakarta.annotation.Nonnull final ValidatePropertiesPostRequest
44
44
post(body, null);
45
45
}
46
46
/**
47
-
* Validate that a Microsoft 365 group's display name or mail nickname complies with naming policies. Clients can use this API to determine whether a display name or mail nickname is valid before trying to create a Microsoft 365 group. For validating properties of an existing group, use the validateProperties function for groups. The following validations are performed for the display name and mail nickname properties:1. Validate the prefix and suffix naming policy2. Validate the custom banned words policy3. Validate the mail nickname is unique This API returns with the first failure encountered. If one or more properties fail multiple validations, only the property with the first validation failure is returned. However, you can validate both the mail nickname and the display name and receive a collection of validation errors if you're only validating the prefix and suffix naming policy.
47
+
* Validate that a Microsoft 365 group's display name or mail nickname complies with naming policies. Clients can use this API to determine whether a display name or mail nickname is valid before trying to create a Microsoft 365 group. For validating properties of an existing group, use the validateProperties function for groups. The following validations are performed for the display name and mail nickname properties:1. Validate the prefix and suffix naming policy2. Validate the custom banned words policy3. Validate the mail nickname is unique This API returns with the first failure encountered. If one or more properties fail multiple validations, only the property with the first validation failure is returned. However, you can validate both the mail nickname and the display name and receive a collection of validation errors if you're only validating the prefix and suffix naming policy.
48
48
* @param body The request body
49
49
* @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
50
50
* @throws ODataError When receiving a 4XX or 5XX status code
@@ -58,7 +58,7 @@ public void post(@jakarta.annotation.Nonnull final ValidatePropertiesPostRequest
* Validate that a Microsoft 365 group's display name or mail nickname complies with naming policies. Clients can use this API to determine whether a display name or mail nickname is valid before trying to create a Microsoft 365 group. For validating properties of an existing group, use the validateProperties function for groups. The following validations are performed for the display name and mail nickname properties:1. Validate the prefix and suffix naming policy2. Validate the custom banned words policy3. Validate the mail nickname is unique This API returns with the first failure encountered. If one or more properties fail multiple validations, only the property with the first validation failure is returned. However, you can validate both the mail nickname and the display name and receive a collection of validation errors if you're only validating the prefix and suffix naming policy.
61
+
* Validate that a Microsoft 365 group's display name or mail nickname complies with naming policies. Clients can use this API to determine whether a display name or mail nickname is valid before trying to create a Microsoft 365 group. For validating properties of an existing group, use the validateProperties function for groups. The following validations are performed for the display name and mail nickname properties:1. Validate the prefix and suffix naming policy2. Validate the custom banned words policy3. Validate the mail nickname is unique This API returns with the first failure encountered. If one or more properties fail multiple validations, only the property with the first validation failure is returned. However, you can validate both the mail nickname and the display name and receive a collection of validation errors if you're only validating the prefix and suffix naming policy.
62
62
* @param body The request body
63
63
* @return a {@link RequestInformation}
64
64
*/
@@ -67,7 +67,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f
67
67
returntoPostRequestInformation(body, null);
68
68
}
69
69
/**
70
-
* Validate that a Microsoft 365 group's display name or mail nickname complies with naming policies. Clients can use this API to determine whether a display name or mail nickname is valid before trying to create a Microsoft 365 group. For validating properties of an existing group, use the validateProperties function for groups. The following validations are performed for the display name and mail nickname properties:1. Validate the prefix and suffix naming policy2. Validate the custom banned words policy3. Validate the mail nickname is unique This API returns with the first failure encountered. If one or more properties fail multiple validations, only the property with the first validation failure is returned. However, you can validate both the mail nickname and the display name and receive a collection of validation errors if you're only validating the prefix and suffix naming policy.
70
+
* Validate that a Microsoft 365 group's display name or mail nickname complies with naming policies. Clients can use this API to determine whether a display name or mail nickname is valid before trying to create a Microsoft 365 group. For validating properties of an existing group, use the validateProperties function for groups. The following validations are performed for the display name and mail nickname properties:1. Validate the prefix and suffix naming policy2. Validate the custom banned words policy3. Validate the mail nickname is unique This API returns with the first failure encountered. If one or more properties fail multiple validations, only the property with the first validation failure is returned. However, you can validate both the mail nickname and the display name and receive a collection of validation errors if you're only validating the prefix and suffix naming policy.
71
71
* @param body The request body
72
72
* @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options.
0 commit comments