Use this procedure to set up Microsoft Purview Data Security Posture Management (DSPM) for Miro AI so AI prompts and responses from Miro appear in Microsoft Purview’s DSPM for AI. After setup, you’ll validate events and learn how to manage the integration.
Prerequisites
Miro
- Enterprise plan with Enterprise Guard enabled.
- You are a Company Admin.
- Microsoft Entra ID is configured as an SSO provider in Miro.
- To enable this feature, contact your Customer Success Manager.
Microsoft
- Active Microsoft Purview license with support for DSPM for AI.
- Microsoft Entra ID tenant ID used for Miro SSO (the GUID that identifies your Microsoft organization/tenant).
- An Entra role that can grant tenant‑wide admin consent to an application.
Set up the integration in Miro
- In Miro, open Enterprise settings → Enterprise integrations.
- Scroll down and then click to toggle on Microsoft Purview DSPM for AI.
- In the Tenant ID box, enter your Microsoft Entra tenant ID.
- Click Connect.
- When prompted, sign in to Microsoft Entra with an account that can grant tenant‑wide admin consent.
- Review the consent for the Miro AI governance application and click Accept.
- Return to Miro and confirm the integration shows Connected.
Validate activity in Microsoft Purview
- In Miro, perform a simple AI action (for example, summarize sticky notes on a board).
- Wait up to 10–30 minutes for ingestion.
- In Microsoft Purview, go to Microsoft Purview → DSPM for AI → Activity explorer (the Purview view that lists AI activities). You can also view information in the Audit logs.
Note: All text‑based prompts and responses across Miro AI features are forwarded to Purview. Currently, image content is not forwarded to Microsoft Purview. - Filter for Recent events and locate activity from Miro (for example, prompt and response).
Manage the integration
- Disconnect: In Miro, go to Enterprise integrations → Microsoft Purview for AI → Disconnect.
- Change tenant: Disconnect first, then Connect again using a different tenant ID.
Troubleshooting
- Integration option missing: Ensure your org has Enterprise Guard and your account can access Enterprise integrations. Ask a Company Admin to grant access.
- Tenant ID mismatch or connect error: The tenant ID must exactly match the Microsoft Entra tenant used for Miro SSO.
- Consent failed or sign‑in loop: Sign in with an account that can grant tenant‑wide admin consent (work with your Microsoft admin).
- No activity visible: Confirm a test AI action was performed by a user who signs in to Miro via the configured tenant; allow 10–30 minutes; verify your Purview license; and check DSPM for AI → Activity explorer.
- Multiple tenants/IdPs: Only one tenant can be configured in Miro. Activity from users who sign in via SSO for other tenants/IdPs is not forwarded.
Known limitations
For more information, see the known limitations section in the overview documentation.