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 07ffb1b
Browse filesBrowse the repository at this point in the historyBrowse files
Microsoft Graph DevX Tooling
authored and
Microsoft Graph DevX Tooling
committed
feat(generation): update request builders and models
Copy file name to clipboardExpand all lines: msgraph_beta/generated/app/calls/item/participants/item/report_synthetic_media/report_synthetic_media_request_builder.py
+3-2Lines changed: 3 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -32,10 +32,11 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, d
Report synthetic media detections for a participant in a meeting call. This action is intended for certified third-party audio and video synthetic media detection bots admitted to the meeting call. The detection bot calls this action to flag a participant whose stream it identifies as AI-generated or synthetic media. The detection result is propagated to all participants via roster updates. After a successful request, the service stores the detection on the participant as a syntheticMediaDetectionInfo object in the participant's syntheticMediaDetection property and delivers it to all participants in a roster update notification. Each request with a new id creates a separate detection record; the service doesn't deduplicate or merge reports. When a participant has multiple detection records, the syntheticMediaDetection property reflects the most recent report. Third-party bots can invoke this action only when the meeting tenant administrator grants the app the Calls.ReportSyntheticMedia.All application permission. The detection bot must be admitted to the call before it can call this action. For more information about registering a calling bot and joining calls, see Calls and online meetings. The bot obtains the call ID and participant ID from the call roster and subsequent participant roster update notifications, and uses the call's id as {call-id} and the participant's id as {participant-id} in the request URL.
36
36
param body: The request body
37
37
param request_configuration: Configuration for the request such as headers, query parameters, and middleware options.
38
38
Returns: None
39
+
Find more info here: https://learn.microsoft.com/graph/api/participant-reportsyntheticmedia?view=graph-rest-beta
Report synthetic media detections for a participant in a meeting call. This action is intended for certified third-party audio and video synthetic media detection bots admitted to the meeting call. The detection bot calls this action to flag a participant whose stream it identifies as AI-generated or synthetic media. The detection result is propagated to all participants via roster updates. After a successful request, the service stores the detection on the participant as a syntheticMediaDetectionInfo object in the participant's syntheticMediaDetection property and delivers it to all participants in a roster update notification. Each request with a new id creates a separate detection record; the service doesn't deduplicate or merge reports. When a participant has multiple detection records, the syntheticMediaDetection property reflects the most recent report. Third-party bots can invoke this action only when the meeting tenant administrator grants the app the Calls.ReportSyntheticMedia.All application permission. The detection bot must be admitted to the call before it can call this action. For more information about registering a calling bot and joining calls, see Calls and online meetings. The bot obtains the call ID and participant ID from the call roster and subsequent participant roster update notifications, and uses the call's id as {call-id} and the participant's id as {participant-id} in the request URL.
57
58
param body: The request body
58
59
param request_configuration: Configuration for the request such as headers, query parameters, and middleware options.
A collection of targeted messages in the chat that are visible only to specific users. Nullable.
55
+
A collection of targeted messages in the chat that are visible only to specific users. Nullable. You can't expand this relationship using $expand. Targeted messages can also be retrieved via the userTeamwork: getAllTargetedMessages API.
56
56
param request_configuration: Configuration for the request such as headers, query parameters, and middleware options.
A collection of targeted messages in the chat that are visible only to specific users. Nullable.
109
+
A collection of targeted messages in the chat that are visible only to specific users. Nullable. You can't expand this relationship using $expand. Targeted messages can also be retrieved via the userTeamwork: getAllTargetedMessages API.
110
110
param request_configuration: Configuration for the request such as headers, query parameters, and middleware options.
111
111
Returns: RequestInformation
112
112
"""
@@ -168,7 +168,7 @@ class TargetedChatMessageItemRequestBuilderDeleteRequestConfiguration(RequestCon
A collection of targeted messages in the chat that are visible only to specific users. Nullable.
171
+
A collection of targeted messages in the chat that are visible only to specific users. Nullable. You can't expand this relationship using $expand. Targeted messages can also be retrieved via the userTeamwork: getAllTargetedMessages API.
A collection of targeted messages in the chat that are visible only to specific users. Nullable.
52
+
A collection of targeted messages in the chat that are visible only to specific users. Nullable. You can't expand this relationship using $expand. Targeted messages can also be retrieved via the userTeamwork: getAllTargetedMessages API.
53
53
param request_configuration: Configuration for the request such as headers, query parameters, and middleware options.
A collection of targeted messages in the chat that are visible only to specific users. Nullable.
95
+
A collection of targeted messages in the chat that are visible only to specific users. Nullable. You can't expand this relationship using $expand. Targeted messages can also be retrieved via the userTeamwork: getAllTargetedMessages API.
96
96
param request_configuration: Configuration for the request such as headers, query parameters, and middleware options.
A collection of targeted messages in the chat that are visible only to specific users. Nullable.
141
+
A collection of targeted messages in the chat that are visible only to specific users. Nullable. You can't expand this relationship using $expand. Targeted messages can also be retrieved via the userTeamwork: getAllTargetedMessages API.
Copy file name to clipboardExpand all lines: msgraph_beta/generated/communications/calls/item/participants/item/report_synthetic_media/report_synthetic_media_request_builder.py
+3-2Lines changed: 3 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -32,10 +32,11 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, d
Report synthetic media detections for a participant in a meeting call. This action is intended for certified third-party audio and video synthetic media detection bots admitted to the meeting call. The detection bot calls this action to flag a participant whose stream it identifies as AI-generated or synthetic media. The detection result is propagated to all participants via roster updates. After a successful request, the service stores the detection on the participant as a syntheticMediaDetectionInfo object in the participant's syntheticMediaDetection property and delivers it to all participants in a roster update notification. Each request with a new id creates a separate detection record; the service doesn't deduplicate or merge reports. When a participant has multiple detection records, the syntheticMediaDetection property reflects the most recent report. Third-party bots can invoke this action only when the meeting tenant administrator grants the app the Calls.ReportSyntheticMedia.All application permission. The detection bot must be admitted to the call before it can call this action. For more information about registering a calling bot and joining calls, see Calls and online meetings. The bot obtains the call ID and participant ID from the call roster and subsequent participant roster update notifications, and uses the call's id as {call-id} and the participant's id as {participant-id} in the request URL.
36
36
param body: The request body
37
37
param request_configuration: Configuration for the request such as headers, query parameters, and middleware options.
38
38
Returns: None
39
+
Find more info here: https://learn.microsoft.com/graph/api/participant-reportsyntheticmedia?view=graph-rest-beta
Report synthetic media detections for a participant in a meeting call. This action is intended for certified third-party audio and video synthetic media detection bots admitted to the meeting call. The detection bot calls this action to flag a participant whose stream it identifies as AI-generated or synthetic media. The detection result is propagated to all participants via roster updates. After a successful request, the service stores the detection on the participant as a syntheticMediaDetectionInfo object in the participant's syntheticMediaDetection property and delivers it to all participants in a roster update notification. Each request with a new id creates a separate detection record; the service doesn't deduplicate or merge reports. When a participant has multiple detection records, the syntheticMediaDetection property reflects the most recent report. Third-party bots can invoke this action only when the meeting tenant administrator grants the app the Calls.ReportSyntheticMedia.All application permission. The detection bot must be admitted to the call before it can call this action. For more information about registering a calling bot and joining calls, see Calls and online meetings. The bot obtains the call ID and participant ID from the call roster and subsequent participant roster update notifications, and uses the call's id as {call-id} and the participant's id as {participant-id} in the request URL.
57
58
param body: The request body
58
59
param request_configuration: Configuration for the request such as headers, query parameters, and middleware options.
Copy file name to clipboardExpand all lines: msgraph_beta/generated/drives/item/items/item/assign_sensitivity_label/assign_sensitivity_label_request_builder.py
+3-2Lines changed: 3 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -32,10 +32,11 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, d
Asynchronously assign a sensitivity label to a driveItem. This API is part of the Microsoft SharePoint and OneDrive APIs that perform advanced premium administrative functions, and is considered as protected. Protected APIs require you to have more validations, beyond permission and consent, before you can use them. For more information about sensitivity labels from an administrator's perspective, see Enable sensitivity labels for Office files in SharePoint and OneDrive. This API applies sensitivity labels to files at rest. Office clients don't apply watermarks, headers, or footers to files that contain the label information. For more information about sensitivity labels from an administrator's perspective, see Enable sensitivity labels for Office files in SharePoint and OneDrive.
36
36
param body: The request body
37
37
param request_configuration: Configuration for the request such as headers, query parameters, and middleware options.
38
38
Returns: None
39
+
Find more info here: https://learn.microsoft.com/graph/api/driveitem-assignsensitivitylabel?view=graph-rest-beta
Asynchronously assign a sensitivity label to a driveItem. This API is part of the Microsoft SharePoint and OneDrive APIs that perform advanced premium administrative functions, and is considered as protected. Protected APIs require you to have more validations, beyond permission and consent, before you can use them. For more information about sensitivity labels from an administrator's perspective, see Enable sensitivity labels for Office files in SharePoint and OneDrive. This API applies sensitivity labels to files at rest. Office clients don't apply watermarks, headers, or footers to files that contain the label information. For more information about sensitivity labels from an administrator's perspective, see Enable sensitivity labels for Office files in SharePoint and OneDrive.
57
58
param body: The request body
58
59
param request_configuration: Configuration for the request such as headers, query parameters, and middleware options.
0 commit comments