If you’re managing Windows 365 Cloud PCs, keeping track of alerts can be a daunting task. Fortunately, Azure Logic Apps can help automate this process by sending alerts directly to your Microsoft Teams channel. In this blog post, we’ll explore how to set up this integration, so you can stay on top of your Windows 365 environment without constantly checking the portal or notifications within the Intune portal.
Note – Within the Microsoft Intune admin center portal you can already send notifications via email.
Set up your Microsoft Teams channel
To start, you’ll need to create a Microsoft Teams channel where you want to receive alerts. If you don’t have one already, create a new channel and name it something like “Windows365Alerts.”
Next, within the newly created channel, add the Connector – Incoming Webhook
Click on Configure of the Incoming Webhook connectors by entering the Name – Win365Alerts and custom image. Why not use the Windows 365 Cloud PC Logo and click on create.
Please copy the link and save it for all future reference purposes. We will be using this URL within the Azure Logic Apps.
https://blahblahblahblah.webhook.office.com/webhookb2/9cd8bac0-XXXX-4e30-XXXX-00700XXXX0@XXXX-d8f4-4c55-XXXX-0eec698XXXXXX/IncomingWebhook/3aXXXXXXXXbed497fbc4d9857XXXXX/57cadd96-b493-4bf6-a665-b0e9XXXXXXX
Azure Active Directory Enterprise App (MS Graph API)
Let’s pre-create the application ID and client secret we will use to connect and leverage the Microsoft Graph APIs via Powershell
- Connect to Azure Portal and go to Azure Active Directory
- Click on App Registrations and select – New Registration
- Give the App a Name – GraphAPI-App
- You will get two important information created for later use within Powershell
- Application ID
- Tenant ID
- Now let’s grant this App GraphAPI-App Permission. Click on Add a permission and select MS Graph and search for Cloud PC– CloudPC.ReadAll and select read permissions and Add Permissions
- Select Grant admin consent for domain
- We are using client secret so now lets enable that. Click on Certificates & Secrets – Client Secrets and select New client secret\
- Give it a name (Deviceconfig_secret) and expiry date (12 months)
- Copy the Secret Value
Azure Key Vault – (Store the Secret)
This is an optional step, and I highly recommend this step for all production environments as the secret is stored within the Azure Key Vault, and within the Azure Logic Apps, you will call this secret.
After creating the value, go to Secret and click on Generate/Import, and under manual, enter a name and paste the secret key we created in the above step.
Additionally, I will dedicate a service account(svc_kv_api) specifically for this secret retrieval for the Azure Logic Apps. Let’s add the service account with the necessary permissions under the Access Policies and give it Get and List permissions.
Create an Azure Logic App
Next, you’ll need to create an Azure Logic App. In the Azure portal, search for “Logic Apps” and click “Create.” Give your Logic App a name and select your desired subscription, resource group, and location. Then click “Review + Create” and “Create” to create your Logic App.
Configure your Logic App
Once your Logic App is created, click “Logic App Designer” and select “When a HTTP request is received” as your trigger. Give your trigger a name and click “Save.” Next, add a new action by clicking the plus sign (+) and search for “Recurrence.” and other operations show below:
Step 1 – Recurrence (A schedule that will be triggered)
Depending upon your SLA agreements, put a trigger. In this example, I have selected every 3 min.
Step 2 – Fetch the Secret from the Azure Key Vault
In the earlier step, we created the Azure Key vault and stored the secret there. In this step, we will make the Azure Logic Apps Fetch the Secret
- Tenant ID – Copy from the above steps
- KeyVault Name – Copy from the above steps
- Click on Sign and use the dedicated service account to fetch this Secret
Step 3 – HTTP Get the Alerts for Windows 365 Using MS Graph API
We shall create the HTTP request using the Windows 365 Alert API – List and authenticate the call using the secret. Enter all the information shown in the screenshot.
https://graph.microsoft.com/beta/deviceManagement/monitoring/alertRecords
Step 4 – We shall Parse the JSON output from the above API GET request
Create the Parse JSON operation, and we will enter the below sample JSON output. Note I have run the GET and got the output from the API. Paste the below code into the schema example. It will auto-generate the below output for your use without values inside.
{
"properties": {
"@@odata.context": {
"type": "string"
},
"value": {
"items": {
"properties": {
"alertImpact": {
"properties": {
"aggregationType": {
"type": "string"
},
"value": {
"type": "integer"
}
},
"type": "object"
},
"alertRuleId": {
"type": "string"
},
"alertRuleTemplate": {
"type": "string"
},
"detectedDateTime": {
"type": "string"
},
"displayName": {
"type": "string"
},
"id": {
"type": "string"
},
"lastUpdatedDateTime": {
"type": "string"
},
"resolvedDateTime": {
"type": "string"
},
"severity": {
"type": "string"
},
"status": {
"type": "string"
}
},
"required": [
"id",
"displayName",
"status",
"severity",
"alertRuleId",
"alertRuleTemplate",
"detectedDateTime",
"resolvedDateTime",
"lastUpdatedDateTime",
"alertImpact"
],
"type": "object"
},
"type": "array"
}
},
"type": "object"
}
Step 5 – Post the Alert to Microsoft Teams using the HTTP operation
Create the HTTP Operation, select POST, enter the webhook URL from the above step on MS Teams, and paste it within the URL. With the Headers add Content-Type: application/json and paste the below body code.
{
"text": "**Alert name:** @{items('For_each')?['displayName']} \n\n **Status:** @{items('For_each')?['status']} \n\n **Severity:** @{items('For_each')?['severity']} \n\n **Detect Date:** @{items('For_each')?['detectedDateTime']} \n\n **Resolved Date:** @{items('For_each')?['resolvedDateTime']} \n\n **Alert Rule Template:** @{items('For_each')?['alertRuleTemplate']} \n\n **Alert Impact:** @{items('For_each')?['alertImpact']}",
"title": "Windows 365 Cloud PC Alerts with status and Severity "
}
Step 6 – Run the workflow
The above will now start running the Azure Logic Apps every 3 mins and keep sending the alerts to Microsoft teams
I need help filtering the alerts based on specific Status and Severity. If you manage to get to that, please message me, and I will happily include those bits in the blog post.
I hope you will find this helpful information for enabling Windows 365 Alerts within the MS Teams using the Azure Logic Apps. Please let me know if I have missed any steps or details, and I will be happy to update the post.
Thanks,
Aresh Sarkari
Recent Comments