Notifications
Configuration → Notifications has four tabs: Email Settings, Actionable Emails, Teams Notifications, and Templates.
Email Settings
Section titled “Email Settings”
- Sender Email Address — the address emails are sent from. Must be a Shared Mailbox or User Mailbox — not an Office 365 Group mailbox (see Prerequisites).
- Approval Requests Email — where deployment-approval requests go. Recommended: an Office 365 Group set to auto-subscribe members.
- Purchase Requests Email — where new-app (procurement) requests go.
- Admin Notifications Email — where admin alerts (e.g. DEP/VPP token expiry) go.
- Service Desk Ticket Email — address used for service-desk ticket creation.
Actionable Emails
Section titled “Actionable Emails”“Actionable” (live) emails update themselves in Outlook and can carry action buttons. This tab manages the Office 365 Provider ID that establishes that trust.

- Create Provider ID — generates the Provider ID using the details below.
- Enable Automatic Refresh for Requestor Emails — keep requestor emails refreshing in place; disable to turn that off.
- Configuration for OAM Portal (the values you enter in Microsoft’s Actionable Email
Developer Dashboard):
- Email Address — your sender address.
- Target URL — your MovoSuite backend URL.
- Scope of Submission — Organization.
After creating the ID in the Developer Dashboard, an Exchange/Global Administrator must approve it; then save the Provider ID back into MovoSuite.
Teams Notifications
Section titled “Teams Notifications”
- Microsoft Teams Configuration — shows whether the MovoSuite bot and the MovoSuite Admins team are configured, with shortcuts to open them in Teams and to Reconfigure Bot / Repair Team. (Both are set up during onboarding.)
- Teams Webhooks (fallback) — if your org disallows bot services, configure incoming webhook URLs for Approval Requests, Purchase Requests, and Admin Notifications. Webhooks are one-way and static — no interactive cards or comments.
Templates
Section titled “Templates”
Customize the email sent for each action.
- Select Template — pick the action (e.g. Purchase Request Completed, Deployment Approval Request, Deployment Completed, Deployment Started, App Request Received, Purchase Request Approval).
- Edit the Subject Line, Custom Message (Markdown supported), and Custom Footer.
- Click Save Template.
The supported notification-template variables are exactly: %appName%, %requestId%,
%requestStatus%, %status%, and %title%. (Device-naming tokens like %serial% or
%assetTag% belong to the separate device-naming subsystem and are not valid in
notification templates.)