Is your Boyum Print & Delivery e-mail on the old Microsoft route? The 5-minute check
If your SAP® Business One invoices or statements go out by e-mail through Boyum’s B1 Print & Delivery (P&D), one setting decides whether they keep going out after Microsoft’s change.
Last checked: 6 October 2026, against Microsoft’s and Boyum’s own posts.
What Microsoft is changing
Microsoft is retiring Exchange Web Services (EWS) in Exchange Online, the mail service behind Microsoft 365. P&D’s Exchange e-mail method uses that route.
| When | What happens |
|---|---|
| From 10 October 2026 | A tenant that keeps EWS on must have an allow list of apps. Apps not on it are refused. |
| After 10 October 2026, tenant by tenant (no fixed date) | Tenants that never changed their EWS setting get a 7-day warning in the Message Center, then EWS is switched off. |
| 1 April 2027 | EWS is removed for everyone. |
These dates are for Microsoft’s worldwide (commercial) cloud. Government and other Microsoft clouds get their own dates in the Message Center.
Microsoft fills many allow lists automatically from the last 60 days of use, so P&D often still works today. But that list may miss jobs that run rarely, like quarterly statements, and Microsoft never adds to a list your IT admin built by hand. Working today is not the same as safe.
Who is affected
Affected: P&D’s Exchange delivery method with a Microsoft 365 mailbox, wherever the e-mail is sent from: a user e-mailing a document, a Mass Delivery run, or a scheduled job in the Boyum Server Component.
Not affected by this change: your own on-premises Exchange Server, Google Workspace, and P&D’s Outlook method (Outlook on the PC sends the e-mail; Microsoft asks that Outlook be kept on a current build). P&D’s SMTP method has its own, separate Microsoft timeline; check it separately.
The 5-minute check
Steps 2 and 3 need a B1UP administrator, usually your SAP admin.
- Is your mail on Microsoft 365? If your work mailbox opens at outlook.office.com, yes. On your own Exchange server or Google, stop here.
- Which route does P&D use? Go to Administration > Add-ons > B1 Usability Package > Module configuration > B1 Print and Delivery > Report Actions and open your invoice e-mail action. Look at both fields, Client delivery method and Server delivery method (scheduled jobs use the second), and at Use Personal Exchange. Repeat for your other e-mail actions and each company database.
Quicker: open the list of Exchange configurations (the “…” button next to the field). An entry with Modern authentication and a Client Id means Exchange is set up on Microsoft 365, and every action that uses it is on the old route.
- Which B1UP version do you run? Help > System Information (B1 Usability Package). The new Graph API method needs 2026.06 HF08 or later.
- Optional, for your Microsoft 365 admin: give the admin that Client Id and ask whether it is on the tenant’s EWS allow list (EWSAllowedAppIDs) and whether EWS is still switched on for the tenant (EWSEnabled).
| You found | What it means |
|---|---|
| Graph API in both fields | Already on the new route. Put the client secret’s expiry date in a calendar. |
| Exchange in either field (with or without Personal Exchange) | Affected. Switch before 1 April 2027. |
| Exchange, and the Client Id is not on the allow list, or EWS is switched off | Sending can be refused now. Act first. |
| SMTP or Outlook | Not this change. |
What to do next
- Upgrade if needed. Your Boyum partner supplies B1UP and the Server Component at 2026.06 HF08 or later, the same build for both. It may need a newer SAP Business One version, so ask before you set a date.
- Microsoft 365. Your admin registers an app for P&D in your own Microsoft 365 tenant (Boyum calls it the B1UP app registration) and gives it the Microsoft Graph Mail.Send application permission with admin consent. By default that lets the app send as any mailbox, so ask the admin to limit it to the mailboxes you send from. Microsoft’s tool for that is RBAC for Applications in Exchange Online; it only restricts the app once the tenant-wide consent is removed, so test sending again afterwards.
- Switch every action to Graph API, in both delivery-method fields, in every company database, including actions used by Mass Delivery and schedules. Switching only the client field leaves the overnight jobs on the old route.
- Test safely: one send from a document, one Mass Delivery run, one scheduled job and one shared-mailbox send, each to a test business partner or an internal address. Never test with a Mass Delivery to real customers.
- Write down the secret’s expiry date. When the client secret expires, sending stops again, often overnight and unnoticed.
Boyum’s step-by-step instructions are in its Help Center article Microsoft is retiring EWS.
A side benefit: the Exchange method signs in as a mailbox user, so a password change or new MFA rule can stop it. Graph, for shared and scheduled sending, signs in as an application.
FAQ
Our invoices still go out. Do we need to do anything? Yes, before 1 April 2027. Today’s sending may rely on Microsoft’s automatic allow list, which is a bridge, not a fix.
How would we notice if it broke? Often not at first: scheduled jobs run at night, and the first sign is a customer saying the invoice never arrived. Check the P&D Delivery Log and Error Log, and, if an error e-mail address is set in the schedule, watch for error e-mails from the Server Component.
Who does the work? Your Boyum partner upgrades, your Microsoft 365 admin grants and limits the permission, and your SAP admin or consultant switches P&D and tests.
If you’d rather not do the check alone, we can do it with you on a short screen-share. Do the check with us
Sources: Microsoft Exchange Team, EWS Deprecation Is Here (updated 3 Oct 2026) and Take control of your EWSAllowedAppIDs list (4 Sep 2026) · Message Center MC1227454 · Boyum, Microsoft is retiring EWS (25 Sep 2026).