Microsoft Purview

Your organisation already says what is Confidential and what is Highly Confidential: in Microsoft Purview, as sensitivity labels on files and mail. Connect AIOE to Purview and those labels become the rule every workbench follows. A labelled file decides where its contents may go, text that carries a label's marking is caught when someone pastes it into a prompt, Purview's own data loss prevention policies can judge a prompt before it goes to a hosted model, and every decision shows up in Purview's Activity explorer beside Copilot's.

What you getCopy Anchor Link

Set it upCopy Anchor Link

GRAPH_SP=$(az ad sp show --id 00000003-0000-0000-c000-000000000000 --query id -o tsv)
az rest --method POST \
  --url "https://graph.microsoft.com/v1.0/servicePrincipals/<service principal id>/appRoleAssignments" \
  --body "{\"principalId\":\"<service principal id>\",\"resourceId\":\"$GRAPH_SP\",\"appRoleId\":\"<role id>\"}"

The DLP policy for Ask Purview itselfCopy Anchor Link

The Purview portal cannot make a DLP policy for an app like AI Workbench: policies made there cover Microsoft 365 only. Make it in PowerShell, on Windows or with PowerShell 7, scoped to the blueprint's application id:

Install-Module ExchangeOnlineManagement -Scope CurrentUser
Connect-IPPSSession -UserPrincipalName <your admin UPN>

$blueprint = "<blueprint application id>"
$apiApp    = "<AIOE API application id>"
$loc = { param($id, $name) "{`"Workload`":`"Applications`",`"Location`":`"$id`",`"LocationDisplayName`":`"$name`",`"LocationSource`":`"Entra`",`"LocationType`":`"Individual`",`"Inclusions`":[{`"Type`":`"Tenant`",`"Identity`":`"All`"}]}" }
$locations = "[" + (& $loc $blueprint "Mojo Up AI Workbench") + "," + (& $loc $apiApp "Mojo Up AI Workbench (AIOE API)") + "]"

New-DlpCompliancePolicy -Name "AI Workbench prompts" -Mode Enable -Locations $locations -EnforcementPlanes @("Application")
New-DlpComplianceRule -Name "Block credentials in prompts" -Policy "AI Workbench prompts" `
  -ContentContainsSensitiveInformation @{Name = "All Credential Types"} `
  -RestrictAccess @(@{setting = "UploadText"; value = "Block"}) -GenerateAlert $true

Name both applications: Purview matches a policy against the application that calls it, and AIOE calls as the blueprint where Microsoft allows it and as the AIOE API application otherwise (Try a prompt says which). To replace a policy made with one location, run Remove-DlpCompliancePolicy -Identity "AI Workbench prompts" and create it again with both.

Keep -Mode Enable: a policy in test mode answers allow. To check the policy before any workbench is involved, use Try a prompt under Ask Purview itself: paste a fake credential, and the panel says whether your prompts are in scope of a policy, Purview's verdict and which policy matched. Nothing you type there is kept. These verdicts are billed on Purview pay-as-you-go, which a Global Administrator turns on once in the Purview portal (the rocket icon, Get Started, then a subscription and resource group). A new policy takes up to an hour to apply. To keep the prompts and the activity AIOE reports for Activity explorer, Insider Risk and eDiscovery, select Secure interactions from enterprise apps in DSPM for AI.

The SharePoint route's billingCopy Anchor Link

Microsoft meters applying a label to a file. Link the AIOE API application to an Azure subscription in the same tenant once:

az provider register --namespace Microsoft.GraphServices   # wait until it shows Registered
az rest --method PUT \
  --url "https://management.azure.com/subscriptions/<subscription>/resourceGroups/<group>/providers/Microsoft.GraphServices/accounts/aioe-graph-billing?api-version=2023-04-13" \
  --body '{"location":"global","properties":{"appId":"<AIOE API application id>"}}'

Until it exists, a job ends with "billing required".

What a person seesCopy Anchor Link

On a workbench, a file under a label the policy keeps home is read by local models only, and a hosted request that would carry it is held, redacted or refused as the mapping says. Pasted text that carries a marking is treated as that label. When Purview blocks a prompt, the person sees Purview's own policy tip. For a label that encrypts, the workbench offers to apply it through SharePoint and shows the job's progress.

DisconnectingCopy Anchor Link

Disconnect forgets the connection; the next policy refresh takes the labels off every workbench. Partner labels and mappings are forgotten with it.

RelatedCopy Anchor Link

• Microsoft setup commands: every command, in order, with the role ids filled in.

• Microsoft Agent 365: the blueprint AIOE reads Purview as.

• Policy: the data-protection section the labels land in.

• Audit: every connect, mapping, location and applied label is a purview.* entry.