'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Microsoft 365 Domain Setup Showing No Services Selected
Question details
The user needs to configure their domain services in Microsoft 365 after the setup wizard finishes prematurely.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Setting up a custom domain in the Microsoft 365 admin center for email and other services.
- Observed behavior
- The domain setup wizard finishes immediately after completing the TXT verification, failing to display the necessary DNS records and leaving the domain marked as having no services selected.
Ensure you have global administrator access to your Microsoft 365 admin center and administrative access to your domain's DNS hosting provider console.
Manually Add Required DNS Records
Bypass the faulty setup wizard by retrieving the necessary DNS records directly from the admin center and adding them to your DNS host.
If the automated wizard fails to guide you through the service selection, you can still finalize your domain setup by manually configuring your MX, CNAME, TXT, and SRV records.
Log in to the Microsoft 365 admin center, navigate to Settings, and select Domains. Click on the domain that is stuck in the setup process.
Look for the DNS records tab or the option to manage DNS. Take note of the specific MX, CNAME, and TXT records Microsoft 365 requires for Exchange Online and other services.
Log in to your DNS hosting provider's management console. Add the Exchange Online MX record and the required CNAME records exactly as displayed in the admin center.
In your DNS host, add a single TXT record for SPF to prevent email spoofing. Ensure the value contains exactly `v=spf1 include:spf.protection.outlook.com -all`.
If you are using specific communication services that require them, add the necessary SRV records to your DNS host, then return to the Microsoft 365 admin center to verify the domain.
Contact Microsoft 365 Support
If manual DNS configuration does not update the domain's service status, contact Microsoft support to resolve backend provisioning errors.
Looking for a Lightweight Office Suite? Try WPS Office
While managing complex Microsoft 365 domain setups and DNS records can be a tedious administrative task, creating and editing your daily documents shouldn't be. WPS Office offers a powerful, lightweight, and completely free alternative for your everyday productivity needs.
Frequently Asked Questions
Why does the domain setup wizard finish immediately after TXT verification?
This usually occurs due to a temporary backend synchronization issue or a glitch in the Microsoft 365 setup wizard that causes it to skip the service provisioning step. Manually configuring your DNS records typically resolves the issue.
Where can I find the specific DNS records my domain needs for Microsoft 365?
You can find the exact DNS values required for your domain in the Microsoft 365 admin center by navigating to Settings > Domains, clicking on your specific domain name, and viewing the DNS configuration tab.
What happens if I add multiple SPF TXT records for my domain?
Having multiple SPF records will cause validation failures, which can result in your outgoing emails being marked as spam or rejected by recipient servers. You must merge all authorized senders into a single SPF TXT record.
