# Teams alert for Intune policy changes | TenuVault Set up a Teams alert for Intune policy changes with TenuVault: add a Workflows destination, filter policies, test delivery, and understand polling delays. Canonical: https://www.tenuvault.com/guides/teams-alert-intune-policy-changes Practical guide # Teams alert for Intune policy changes A Teams alert for Intune policy changes needs a Teams Workflows destination, a TenuVault alert and Intune change watching enabled. Watching polls audit events, every 15 minutes by default in the app. Delivery follows a check and any destination retries, so this is not an instant alert. [Start free Pro trial](https://www.tenuvault.com/trial?src=feature)[Plans and features](https://www.tenuvault.com/pricing) ## What does the native audit log tell me? Microsoft records policy change activity in Intune audit logs. An administrator can review events in the admin center and route audit logs to Azure Monitor. That provides an investigation source, but your operational procedure still needs to decide which events deserve attention and who should receive them. This guide focuses on a Teams destination for selected policy changes. For investigating who changed a policy, use the separate audit guide. A message tells the on-call administrator where to look; it does not replace a configuration backup or prove that devices have received the change. ## How do I set up a Teams alert for Intune policy changes? 1\. In the intended Teams channel, open Workflows and choose the template that posts to the channel when a webhook request is received. Name the workflow and copy its URL. Choose an owner whose account lifecycle your team manages. 2\. In TenuVault, select the tenant and open Alerts, then Channels. Add a Teams channel and paste the Workflows URL. Notifications require Pro; check the pricing page before planning deployment across tenants. 3\. In Alerts, add an alert using Every Intune change, one by one or another suitable template. Select the Teams destination and the event types you need. Enable Intune watching on the Change watching tab and confirm the polling interval. ## How do I alert on one policy without hiding deletions? Use Policy names to choose the scope. Contains matches names containing the entered text. Exact name matches the chosen name, ignoring case and surrounding spaces. A rename stops an exact-name alert until you update its filter, so include that maintenance step in your change process. Avoid Changed settings contain if the alert must catch deletions or assignment removals. Only updates name changed settings, so those other change types cannot pass that filter. Watching-level audit categories also limit what is read at all. An alert cannot recover a category excluded by change watching. ## How can I check the message and delivery path? Use Check the last 7 days to see what the current alert would have selected without sending old messages. Then use Send test to inspect the Teams card. Check Deliveries for the sent event, failures and retries, rather than assuming that saving a channel proves the destination works. One alert per change sends up to 20 individual alerts per check, with overflow grouped into a summary. Notifications can be delivered more than once after an ambiguous destination response. Settings Catalog updates do not name changed settings from the audit event, but the change itself is still reported. Values are not sent. ## How can I try this on my tenant? Download TenuVault and test with an approved unassigned policy. Record the edit time, wait for a scheduled check or use Poll now while desktop watching owns the tenant, and verify the policy name and operation in Teams. Keep TenuVault running and signed in during the desktop test. If a test fails, inspect the channel response and Deliveries. A workflow can stop when its owner account is disabled, and tenant policy can block Workflows. For coverage while the computer is off, configure the documented Azure watcher separately. A desktop alert rule alone does not create an independent cloud runner. - [Change alert features](https://www.tenuvault.com/intune-alerts) - [Investigate who changed a policy](https://www.tenuvault.com/guides/who-changed-intune-policy) - [Compare configuration versions](https://www.tenuvault.com/guides/intune-policy-version-history) - [Microsoft Intune audit logs](https://learn.microsoft.com/en-us/intune/governance/monitor-audit-logs) - [Download TenuVault](https://www.tenuvault.com/download) ## Read the technical guides - [Detailed product documentation](https://docs.tenuvault.com/notifications/) Product scope reviewed 11 November 2026. Check your installed release and the current plan table before using a workflow. ## Frequently asked questions ### Q: Are Teams alerts immediate? A: No. Change watching polls the audit logs. The desktop default is every 15 minutes, with delivery and retry time afterward. ### Q: Will an alert include setting values? A: No. Change alerts can name changed settings but do not send the old or new values. Use a change report for reviewed before-and-after evidence. ### Q: What if the computer is asleep? A: Desktop watching stops. Use the Azure watcher for scheduled checks independent of the computer, and verify the handover and first run. ## Related guides - [get notified about Intune changes](https://www.tenuvault.com/intune-alerts) - [Watch Intune changes while your PC is off](https://www.tenuvault.com/guides/watch-intune-changes-pc-off) - [Weekly Intune change report by email](https://www.tenuvault.com/guides/weekly-intune-change-report-email) - [Who changed an Intune policy](https://www.tenuvault.com/guides/who-changed-intune-policy) ## Review your setup before the first change Community is free for one tenant. Try Pro free by connecting a new tenant in the app, no email or card needed. Tenant access, supported restore types and scheduling requirements still apply. [Start free trial](https://www.tenuvault.com/trial?src=cta)[Book a 30-minute demo](https://cal.com/ugur-koc/tenuvault-demo)[Permissions and data flows](https://www.tenuvault.com/trust)