As of 13 August 2026, AI can only partly set up Microsoft 365 email.

What to actually do

1. Hand it to a person

   The route this page recommends

   A person who owns the outcome does this end to end, worth it when the failure is dear.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

   A chat interface, chat-fluent skill, and roughly 1 hour until you can act on the result.

   How to actually do it

   1. Open the Microsoft 365 admin centre and your domain registrar's DNS management page, then record the tenant status, domain name, current MX record and the administrator account you will use without copying any password or secret into the chatbot.
   2. Paste the prompt with your domain, current mail provider, required users, aliases, shared mailboxes, devices and access status filled in, then ask the chatbot to produce the ordered plan and identify any missing information.
   3. Compare the plan's proposed mailbox and licence requirements with the users you actually need, and remove any account, alias or shared mailbox that you cannot authorise.
   4. Follow the Microsoft 365 domain setup instructions to obtain the verification and mail-authentication values, then enter only those values at the registrar and leave the existing MX record unchanged until the migration point is clear.
   5. Create the users, mailboxes, aliases, shared mailboxes, MFA settings and recovery methods in the Microsoft 365 admin centre, then configure Outlook and mobile devices using each user's normal Microsoft sign-in.
   6. After DNS changes have propagated, compare the live DNS records with the values shown by Microsoft 365, then test internal and external sending, replies, aliases, shared mailboxes, spam handling and sign-in before changing or retiring the old mail service.

   Prompt

   Help me set up Microsoft 365 email for a UK business. Give me a safe, ordered plan and do not ask me to paste passwords, access tokens, recovery codes or other secrets.
   
   My situation:
   - Domain: [example.co.uk]
   - Domain registrar or DNS host: [provider]
   - Microsoft 365 tenant status: [new or existing]
   - Current email provider: [provider or none]
   - Users and mailbox addresses needed: [list]
   - Aliases or shared mailboxes needed: [list]
   - Devices and mail apps to support: [list]
   - Whether mail is already in use on this domain: [yes or no]
   - Whether I have Microsoft 365 administrator access: [yes or no]
   
   Separate the plan into:
   1. Microsoft 365 tenant and domain preparation
   2. User, licence, mailbox, alias and shared-mailbox setup
   3. DNS changes, including only records that are actually required
   4. Outlook and mobile setup
   5. MFA, recovery and minimum security settings
   6. Testing and rollback
   
   For every step, name the Microsoft 365 admin centre or DNS area to open, the value I need to obtain or enter, and what success looks like. Clearly label anything that depends on my Microsoft 365 plan or current DNS provider. Explain how to avoid disrupting existing mail and when to change MX records. Include a checklist for testing internal mail, external mail, replies, aliases, shared mailboxes and spam handling. Include SPF, DKIM and DMARC guidance, but do not invent record values: tell me where to obtain each value from Microsoft 365. Flag any step that should be checked by a Microsoft 365 administrator. Use current, cautious instructions and say when I should consult Microsoft documentation rather than guessing.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.