A white and gray multifunction printer on a glass desk, with the paper tray open and the scanner lid on top.
  • Security
  • Microsoft 365
  • Small and Medium Businesses

The printer that scans to email may stop in January: what changes in Microsoft 365 at the end of December

At the end of December 2026, Exchange Online turns off Basic authentication for SMTP AUTH by default on accounts that already exist. The printer that scans to email, the invoicing system, and the website form may stop sending in January.

Photo: Mahrous Houses · on Unsplash

At the end of December 2026, Exchange Online will turn off Basic authentication for SMTP AUTH by default on Microsoft 365 accounts that already exist. The Exchange Team post, Updated Exchange Online SMTP AUTH Basic Authentication Deprecation Timeline, from January 27, 2026, is the source of that timeline.

For someone running a small or mid-sized business in Brazil or Latin America, without a large IT team, the practical point is this. The printer that scans a document and emails it, the business or accounting system that emails invoices and payment slips, the website contact form, the alarm panel or camera that sends an email alert, and an old script may stop sending on the first business days of January, if they still sign in to mail with a username and password.

In this article, “company account” is what Microsoft calls a tenant. SMTP AUTH is the sign-in a device or a program uses to send mail through Exchange Online, at smtp.office365.com. Basic authentication is that sign-in done with a username and password. OAuth is the sign-in method Microsoft points to instead.

This article does not describe a CGT client. The facts come from the January 27 post and from the same team’s earlier post, Exchange Online to retire Basic auth for Client Submission (SMTP AUTH), which records the error a device receives when Basic authentication is refused.

What changes at the end of December 2026

The January 27 post marks four moments. It says they apply to accounts on the service, in every cloud environment.

  • From now through December 2026, behavior stays as it is. Basic authentication for SMTP AUTH remains unchanged.
  • At the end of December 2026, it is turned off by default on accounts that already exist. An administrator can still turn it back on, if needed.
  • An account created after December 2026 does not have that option available by default. The supported method is OAuth.
  • In the second half of 2027, Microsoft will announce the date when Basic authentication for SMTP AUTH is removed for good. The post does not give that date yet.

On November 19, 2026, Microsoft replied in the comments on that post that it is finalizing the details and will share the exact procedure soon. In the same reply, with the procedure still open, Microsoft said there was no plan at that moment for a company to stop the change in advance, and that an administrator would turn the option back on after it had been turned off. The January 27 timeline still stands until that procedure is published.

Turning Basic authentication back on is a stopgap. The post places final removal in the announcement scheduled for the second half of 2027. The time until then is the window for changing how mail is sent, and for testing it.

What this means for the business

The person running the company usually sees the problem on the device, on the day a document does not arrive. These are the common uses in an SME when sending still happens with a username and password at smtp.office365.com:

  • The multifunction printer that scans to email. The contract, the invoice, and the receipt leave the scanner glass and go to an address. If Basic authentication drops, the scan can stay on the machine.
  • The business or accounting system that emails invoices and payment slips. The customer is waiting for the message. The system can report a send failure without anyone having changed the password.
  • The website contact form. The visitor’s message stops arriving in the inbox of the person who answers it.
  • The alarm panel, the camera, or another panel that alerts by email. The event notice stops going out.
  • An old script or program that someone set up with the company email address and a password.

The January post says that, through the end of December, behavior stays the same. The end of December lands on the year-end break. A company that closes between Christmas and New Year can see the effect on the first business days of January, when the printer and the finance desk start sending again.

If Microsoft 365 security defaults are on, Basic authentication for SMTP AUTH is already blocked. In that case, a device that depends on it is already failing today. The end of December is no longer the first notice.

The change the post describes is Basic authentication. OAuth is the method Microsoft points to. A line on the report that already shows OAuth is on the supported method. A line that shows Basic authentication needs a decision before the break.

The error the printer or the system starts to show

When Basic authentication is refused, the Exchange Team’s earlier post records the response the device or the program receives:

550 5.7.30 Basic authentication is not supported for Client Submission.

The addresses that post cites for sending with SMTP AUTH are smtp.office365.com and smtp-legacy.office365.com. On the printer, the field is often filled in with smtp.office365.com.

The English sentence is the signal. In the working day, it means Microsoft refused a send that used a username and password. A new password, typed into the printer again, is still Basic authentication.

How to see what still signs in with a password

The names below are in English, as in Microsoft’s posts. In an admin center set to another language, the same items appear translated.

  1. Open the submission report. In the Exchange admin center: Reports, Mail flow, and the SMTP AUTH clients submission report. The earlier post says this report shows whether a submission uses Basic authentication or OAuth.

  2. Check sign-in logs in Microsoft Entra. Filter by the client app Authenticated SMTP. The list shows which accounts still sign in along that path.

  3. See whether security defaults are on. With them on, Basic authentication for SMTP AUTH is already blocked. The report shows what is still trying to sign in that way.

  4. Fill in what the report does not name. The mailbox appears. The name of the printer, the system, or the script may not. A list made at the company ties the report to the device.

Someone who cannot open the admin center asks the person who administers the Microsoft 365 account for this reading. That account’s password does not go out by message.

Paths Microsoft points to

The earlier post sums up what to do. In language for the person running the business:

  • Update the device or the program to OAuth, when the maker already offers that way of signing in.
  • Switch to a device or a program that supports OAuth, when the one on the wall or in the system will not get that update.
  • Use an alternative Microsoft names. The post cites High Volume Email and Azure Communication Services Email. In the same text, High Volume Email is the service for messages inside the company. When mail also has to reach a customer, a supplier, or a visitor on the website, the post points to a dedicated high-volume solution or to Azure Communication Services Email. The Azure Communication Services retirement guide, announced in September 2026, sets removal of that service’s email for September 30, 2028. For a program the company can change, the website or the script, Microsoft Graph is another way to send, in place of SMTP with a password.
  • A company that still has Exchange installed on its own premises, in a hybrid setup, finds in the same post the option to authenticate to that server. That path needs someone who administers the server. A company that only uses Microsoft 365 in the cloud follows the other items on this list.

Turning Basic authentication back on, once the procedure is published, covers the break. The removal announcement in the second half of 2027 stays on the calendar. A device that only knows a username and password still needs a lasting path.

What to do before the year-end break

The order below fits a company without a large IT team. The exact procedure for turning Basic authentication back on has not been published.

  1. List what sends email in the company’s name. A printer that scans to email, the business system, accounting, invoices, payment slips, the website form, an alarm, a camera, a script. Write down each one’s sending address. smtp.office365.com belongs on the list.

  2. Read the SMTP AUTH clients submission report and the Entra sign-in logs filtered by Authenticated SMTP. Separate what is on Basic authentication from what is already on OAuth.

  3. Talk to the people who maintain the printer and the system. The question is direct: does the model accept OAuth for sending mail through Microsoft 365, is there an update, or is the path a different one. The same question applies to the website form and the script.

  4. Test before the break. One scan to an internal mailbox and, if the system has a test send, one send of whatever produces invoices or payment slips. A test done after the break comes after the window in which the change takes effect.

  5. Agree who looks on the first business days of January. One person checks the printer. Another checks whether invoices and payment slips went out. Both know whom to tell if error 550 5.7.30 appears. The names are written down before the break.

  6. Treat turning Basic authentication back on as a reserve, with a date to leave it. It depends on the procedure Microsoft said, on November 19, 2026, it would still publish. The reserve does not replace the conversation with the maker, or the test.

Frequently asked questions

What changes in Microsoft 365 at the end of December 2026?

Exchange Online turns off Basic authentication for SMTP AUTH by default on accounts that already exist. An administrator can turn it back on. Through the end of December, the January 27 post says behavior stays the same. The exact date inside that month-end, and the steps to turn it back on, are what Microsoft said on November 19, 2026 it would still publish.

Will the printer that scans to email stop?

It may stop, if it sends through smtp.office365.com with a username and password. The same applies to the system that emails invoices or payment slips, the website form, the alarm, the camera, and an old script. With security defaults on, that password-based send is already blocked. If the report shows OAuth, that line uses the method Microsoft points to.

What error appears when Basic authentication is blocked?

The Exchange Team post records the response 550 5.7.30 Basic authentication is not supported for Client Submission. The addresses it cites are smtp.office365.com and smtp-legacy.office365.com.

Can Basic authentication be turned back on?

The January 27 post says an administrator of an account that already exists can still turn it on, if needed. On November 19, 2026, Microsoft replied in the comments that it is finalizing the details and will share the exact procedure soon. Turning it back on is a stopgap: in the second half of 2027 Microsoft announces the date of final removal.

Does a new account, created after December 2026, have this option?

The post says an account created after December 2026 does not have Basic authentication for SMTP AUTH available by default. The supported method is OAuth.

When is Basic authentication removed for good?

The post marks the second half of 2027 as the moment Microsoft announces the removal date. That date is not in the text yet.

Does this describe a CGT client?

No. There is no case, client, or result from CGT in this article.

Another Microsoft 365 change, on another screen, is baseline security mode. The piece on Baseline security mode 2026 covers the controls an administrator simulates before turning them on. The subject of this article is sending email with a username and password, on the SMTP AUTH report.

How CGT can help

CGT supports small and mid-sized businesses on Microsoft 365, within the scope agreed with each client: inventory what still sends email with a username and password, read the SMTP AUTH report, and agree with the people who maintain the printer or the system on a migration path, with a test before the break. Human support is Monday to Friday, 8:00 to 18:00, São Paulo time.

Want an inventory of what may stop sending in January? Meet CGT and talk to us.

Sources: Microsoft Exchange Team — Updated Exchange Online SMTP AUTH Basic Authentication Deprecation Timeline (Jan 27, 2026), Microsoft Exchange Team — Exchange Online to retire Basic auth for Client Submission (SMTP AUTH), and Microsoft Learn — Azure Communication Services retirement and breaking changes.

Next step

Want to get your company’s IT in order?

CGT takes over the operation or reinforces the team you already have. Service is remote, in Portuguese, Spanish and English.