Support Modern Authentication (OAuth 2.0) for email sending in B1UP Server Component Respondida

Asecom Service

Description

The B1UP Server Component currently relies on SMTP Basic Authentication (username/password) to send error notification emails when server tasks fail. This is the only available method for email delivery from the Server Component.

Microsoft has announced that SMTP AUTH Basic Authentication will be disabled by default for existing Exchange Online tenants at the end of December 2026, with a final removal date to be announced in the second half of 2027.

While B1UP already supports Modern Authentication (OAuth 2.0) in the B1 client for Print & Delivery (since version 2020.05), this capability is not available in the Server Component. This means that all customers running automated B1UP server tasks that depend on error email notifications will lose this functionality once Microsoft enforces the deprecation.

Business impact

Error email notifications are a critical part of the monitoring process for automated B1UP server tasks. Without them, process failures go undetected until they cause downstream issues. This affects a large number of B1UP customers who use Exchange Online (Microsoft 365).

Current workarounds such as setting up an internal SMTP relay or a Microsoft 365 connector are possible, but they introduce additional infrastructure, maintenance overhead, and can negatively impact the Microsoft Secure Score of the customer's tenant. These are not sustainable long-term solutions.

Request

Please extend Modern Authentication (OAuth 2.0) support to the B1UP Server Component, specifically for the email sending functionality used in error notifications. This would bring the Server Component in line with the existing Modern Authentication support in Print & Delivery and ensure continued compliance with Microsoft's authentication requirements.

Comentarios

2 comentarios

  • Comment author
    zendesk integration
    Thank you for your request. It has been scheduled for review by the development team that will get back to you should there be questions.
    (Please note that as we are user-driven we can't guarantee that your request will be met unless it gets many votes and/or fit the product vision)
    Read more about the Feature Request process here
    [Internal Id: 163572]
    0
  • Comment author
    Mads Michelsen

    Thanks for the detailed request and for outlining the impact so clearly.

    We fully agree on the importance of supporting Modern Authentication for the Server Component. This feature has already been added to our backlog, and we will make sure it is addressed in a future update to ensure continued compatibility with Microsofts upcoming changes.

    Appreciate you bringing this forward!

    0

Iniciar sesión para dejar un comentario.