Security posture for Microsoft 365 Copilot, Copilot Studio and Azure AI
73 read-only checks across seven surfaces, plus an inventory of the agents in your tenant and the AI apps your people use outside it.
Challenge and solution
Challenge
Copilot answers with whatever the user can already reach, so oversharing, weak Entra settings and unlogged AI use become AI risks. Agents built in Copilot Studio and Azure add more access that nobody reviewed.
Solution
Aynigma connects read-only, runs 73 checks and lists findings for your team to review. It also inventories agents from four sources and finds AI apps in use outside your tenant. Nothing in the tenant is changed.
Key capabilities
Azure AI: 17 checks
Azure AI configuration, read through Azure RBAC.
Entra ID: 16 checks
Entra ID configuration relevant to AI access, read through Microsoft Graph.
Microsoft 365 Copilot and Purview: 14 checks
Microsoft 365 Copilot and Purview settings, read through Microsoft Graph and Purview.
Copilot Studio: 9 checks
Copilot Studio configuration, read through the Power Platform APIs.
Azure platform, shadow AI and logging: 17 checks
Azure platform settings (7), shadow AI exposure (6) and logging coverage (4). The surfaces total 73 checks.
Read-only access model
Access goes through Microsoft Graph, Power Platform APIs, Azure RBAC and Purview. Checks read configuration and produce findings for your team to review.
Licence readiness
Shows whether your tenant holds the Microsoft licences the checks rely on, before you plan the work.
Agent inventory from four sources
Combines the Power Platform inventory, the Microsoft 365 agent registry, the Purview audit log and SharePoint .agent files into one list.
Shadow AI discovery
Upload DNS or proxy logs to match them against a 70-app catalog, or bring a Defender for Endpoint or CSV device export to match against 43 device apps.
Posture change reports
Compare your posture between runs to see what changed.
What you get
A findings list for your team
Each finding names the setting, the surface and what to review. Your team decides what to change.
An inventory of Microsoft agents
One list of agents from four sources, so you can assign owners and find the ones nobody owns.
A view of AI use outside your tenant
Matched apps from your own logs and device exports, instead of a guess.
A record of change over time
Posture change reports show what changed between runs.
Frequently asked questions
What access does Aynigma need?
Read-only access through Microsoft Graph, the Power Platform APIs, Azure RBAC and Purview. Your tenant admin grants the access.
Does Aynigma change anything in my tenant?
No. The checks only read configuration and produce findings. Your team reviews each finding and decides what to change.
Which Microsoft licences do I need?
It depends on the surface. The licence readiness check shows which of the licences these checks rely on your tenant holds, so you know what can run before you start.
How long does a review take?
It depends on the size of the tenant and how many surfaces you connect. We can scope it with you before you grant any access.
Review your Microsoft AI posture.
We scope the surfaces with you before any access is granted.