sendCustomNotificationToCompanyPortal action
Namespace: microsoft.graph
Important: APIs under the /beta version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported.
Note: The Microsoft Graph API for Intune requires an active Intune license for the tenant.
This API is available in the following national cloud deployments.
Global service | US Government L4 | US Government L5 (DOD) | China operated by 21Vianet |
---|---|---|---|
✅ | ✅ | ✅ | ✅ |
Permissions
One of the following permissions is required to call this API. To learn more, including how to choose permissions, see Permissions.
Permission type | Permissions (from most to least privileged) |
---|---|
Delegated (work or school account) | |
Device management | DeviceManagementManagedDevices.ReadWrite.All |
Delegated (personal Microsoft account) | Not supported. |
Application | |
Device management | DeviceManagementManagedDevices.ReadWrite.All |
HTTP Request
POST /deviceManagement/sendCustomNotificationToCompanyPortal
Request headers
Header | Value |
---|---|
Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
Accept | application/json |
Request body
In the request body, supply JSON representation of the parameters.
The following table shows the parameters that can be used with this action.
Property | Type | Description |
---|---|---|
notificationTitle | String | |
notificationBody | String | |
groupsToNotify | String collection |
Response
If successful, this action returns a 204 No Content
response code.
Example
Request
Here is an example of the request.
POST https://graph.microsoft.com/beta/deviceManagement/sendCustomNotificationToCompanyPortal
Content-type: application/json
Content-length: 164
{
"notificationTitle": "Notification Title value",
"notificationBody": "Notification Body value",
"groupsToNotify": [
"Groups To Notify value"
]
}
Response
Here is an example of the response. Note: The response object shown here may be truncated for brevity. All of the properties will be returned from an actual call.
HTTP/1.1 204 No Content
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for