Administrator guide: deploying Prudai for Outlook

This page is for IT administrators at a customer organization. End users do not need these steps — for them, see getting started for users. What the add-in does is covered on Prudai for Outlook.

Central deployment via the Microsoft 365 Admin Center

1. Go to the Microsoft 365 Admin Center (admin.microsoft.com).
2. Navigate to Settings → Integrated apps.
3. Choose Upload custom apps, app type Office Add-in, then Provide link to manifest file.
4. Enter the manifest URL: https://app.prudai.com/outlook-addin/manifest.production.xml Once the add-in is published in Microsoft AppSource, you can instead find and deploy it via Get apps on the same screen.
5. Choose the assignment: the entire organization, specific groups, or individual users.
6. Review the requested permissions and complete the wizard.

Rollout takes time: Microsoft distributes the add-in in the background. This usually takes a few hours, but in some tenants it can take up to 24 hours before the add-in is visible in Outlook for all users.

What the manifest requests:

• Office permission ReadWriteItem (read the open message and edit drafts),
• minimum Outlook requirement set Mailbox 1.5 (so it also works on older Outlook clients; some features require a newer client and hide themselves automatically when it is missing).

Access & licenses

The add-in grants no access of its own: users sign in with their Prudai account and need an active LEO license. Anyone without platform access cannot use the add-in — the assignment in the Admin Center only determines who sees the add-in in Outlook.

If your organization uses Microsoft SSO for Prudai, that configuration applies here too — see setting up SSO (Microsoft) + SharePoint.

Network access

Allow outbound HTTPS traffic to:

Domain	Used for
app.prudai.com	the add-in itself (task pane and manifest)
login.prudai.com	Prudai sign-in (Keycloak)
login.microsoftonline.com	Microsoft authentication

Optional: Microsoft mail connection (full conversations)

Without extra configuration, the add-in works with the open message: saving, summarizing, and replying to the email the user has in front of them.

If you want users to also be able to save and summarize full conversations (all messages in a thread, including ones that are not open), there are two preconditions — both are required:

1. Activation on the Prudai side. The Microsoft mail connection must be enabled for your organization by Prudai (just like the SharePoint connection). Contact support or your Prudai contact to arrange this.
2. Read access via Microsoft Graph on your side:
   • In your organization’s Entra app registration (the same one used for SSO/SharePoint — see the SSO guide), add the delegated Graph permission Mail.Read.
   • Click Grant admin consent for your tenant. Without admin consent, users get a consent prompt or a denial.

This is a delegated permission: Prudai only reads mail belonging to the signed-in user, and only at the moment that user explicitly asks for it in the add-in (for example “save the entire conversation”). There is no background synchronization of mailboxes.

If you skip these steps, the add-in keeps working with the open message. “Entire conversation” options may still be visible in the add-in, but using them falls back to the open message only — the user sees a notice when that happens.

When to use central deployment

Central deployment is recommended when you:

• want the add-in available by default for (part of) the organization,
• have disabled self-service installation for users,
• do not want to hand out individual manifest files per user.

For pilots, an administrator can also assign the add-in to a small test group first and widen the assignment later.

More: Prudai for Outlook · Getting started for users · Troubleshooting & support.