Hi @Mike Jaap,
Thank you for posting your question in the Microsoft Q&A forum.
Based on the details you shared that you are unable to send or receive email in the new Outlook on Windows 10 even though your account shows as Active. I truly understand and appreciate your effort in testing on your side and sharing clear information. This typically occurs when Exchange Online is not fully assigned or provisioned, when the mailbox is inactive or still being created, or when authentication or an outdated Outlook profile interrupts the connection. It can also result from DNS misconfiguration, policy restrictions, a full mailbox, or required legacy protocols such as SMTP or IMAP being disabled.
Please follow the steps below in order. If you are not an administrator, kindly share the administrator steps with your IT team. After each step, please test send and receive so I can identify the exact cause.
1/ Quick isolation test in Outlook on the web
- Go to https://outlook.office.com and sign in with the affected account.
- Send a test email to your own address and another to a colleague.
- If this works, the issue is likely local to the Outlook app, so move to Step 6. If this fails, continue with the next steps since it is likely a service or configuration issue.
2/ Confirm license and Exchange service assignment (Admin Only)
- Open the Microsoft 365 admin center.
- Go to Users, select Active users, choose the affected user, then open Licenses and apps.
- Ensure the user has a license that includes Exchange Online and that Exchange Online Plan 1 or Plan 2 is enabled under Apps.
- Save changes, wait fifteen to thirty minutes for provisioning to complete, and retest in webmail.
Note that plans such as Business Standard, E3, or E5 still require the Exchange Online app toggle to be on.
3/ Verify the mailbox exists and is active (Admin Only)
- Open the Exchange admin center.
- Go to Recipients, then Mailboxes, and search for the user.
- Confirm the mailbox shows Active and is not soft deleted or inactive.
- If it is missing, enable Exchange Online as described in Step 2, allow time for provisioning, and test again in webmail.
4/ Check domain DNS if you use a custom domain (Admin)
- At your DNS provider, verify these records.
- MX should point to your Microsoft value that ends with mail protection outlook com.
- SPF should include include colon spf dot protection dot outlook dot com.
- Autodiscover CNAME should point to autodiscover dot outlook dot com.
- Correct any inaccurate record, allow DNS to propagate, and then retest because DNS issues can block inbound mail and cause outbound rejections.
5/ Review mail flow restrictions and blocks (Admin)
- In the Exchange admin center, open Mail flow and then Rules, and check for any rule that blocks this user.
- In the Microsoft Defender portal at https://security.microsoft.com, go to Email and collaboration, then Review, then Restricted entities or Restricted users.
- If the user is restricted, remove the restriction and test again.
6/ If Outlook for desktop or mobile is the only client failing
- Update Office apps to the latest version through Microsoft Store or Office Update.
- Remove the account from the new Outlook, close Outlook, and add the account again.
- Create a new Outlook profile through Control Panel, Mail, Show Profiles, Add, set it as the default, and test again.
- For legacy devices or applications such as printers, scanners, or line of business tools, ensure SMTP authentication is enabled for the mailbox in the Exchange admin center. If the device does not support modern authentication and your policy allows it, use an app password.
7/ If the issue persists
Please have your administrator open a support request in the Microsoft 365 admin center under Support, New service request. Microsoft can review message traces and tracking logs, provisioning and back end health, tenant level anti spam and transport settings, and any hidden corruption that requires engineering tools.
They can also raise a support ticket by visiting: Get support - Microsoft 365 admin | Microsoft Learn
As community moderators, we appreciate your understanding that our access to internal development details is limited. Our primary role is to guide users toward the appropriate resources and support channels. While we may not have visibility into deeper backend analysis, we’ll continue doing our best to support you within the scope of our responsibilities.
I hope this information is helpful. Please follow these steps and let me know if it works for you. If you have any updates regarding the issue, please feel free to share them with me.
Thank you for your patience and your understanding. I look forward to continuing the conversation.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment”.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.