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
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.

In Outlook, the button Prudai voor Outlook appears in the Prudai group, both when reading and when composing a message. The add-in’s ribbon labels are in Dutch only.

What the manifest requests:

• Office permission ReadWriteItem (read the open message and edit drafts),
• minimum Outlook requirement set Mailbox 1.5. The add-in therefore also works on older Outlook clients. Some features need a newer client and hide themselves automatically when it is missing; for instance, the Attachments only choice only appears when Outlook can hand attachments to the add-in and the message has at least one attachment of a supported file type.

Current manifest version: 1.1.0.2.

Also rolling out Word or Excel? They follow the same steps, with their own manifest URL. See Prudai For Word and Prudai for Excel.

Access & licenses

The add-in grants no access of its own: users sign in with their Prudai account and need an active license for a persona the add-in works in: LEO, LEO Fiscaal, ZIA, VERA or BEVER. 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)
api.prudai.com	the assistant, dossiers (projects), and saving email
api.account.prudai.com	account and organization data
login.prudai.com	Prudai sign-in
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, and use them as the basis for a draft reply (all messages in a conversation, 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. In the Account Dashboard, the owner sees it under Capabilities as Outlook Integration; see Account & RAG dashboards.
2. Read access via Microsoft Graph on your side:
   • An administrator grants consent on behalf of the organization for the delegated Graph permission Mail.Read, for the same Prudai app used for SSO and SharePoint (you do not create an app registration of your own, see the SSO guide): Enterprise applications → Prudai’s app → Permissions → Grant admin consent for <tenant>.
   • If Mail.Read is not in the list Microsoft then shows you, ask support for a consent link. Without consent on behalf of the organization, users get a consent prompt or a denial.

After that, each user makes the connection themselves by signing in via Microsoft (not with a username and password). Users who sign in differently simply work with the open message.

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

Per conversation, the add-in retrieves at most 100 messages. If a conversation is longer, the add-in tells the user.

What users see when a precondition is missing:

• Not activated by Prudai: the Entire conversation choice does not appear; summarizing and replying use only the open message.
• Activated, but no consent or not signed in via Microsoft: the Entire conversation choice is there but falls back to the open message. After saving, the user then sees “Only the current message was saved.” and “Connect Microsoft mail to save entire conversations.” Summarizing and replying in that case use only the open message, without a notice.

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, you 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.