logo
search
Send & Receive Issues

How to Set Up Automatic Replies for a Microsoft 365 Email Alias

Adam DavisAdam Davis Oct 22, 2026 868 views

Question details

The user wants to configure a distinct automatic reply message for emails sent to an alternative email alias on a primary Microsoft 365 mailbox.

How to Configure Automatic Replies for a Microsoft 365 Email Alias
Product
Microsoft 365
Device & OS
not provided
Scenario
Configuring out-of-office or automatic reply messages specifically for a secondary email address (alias).
Observed behavior
Microsoft 365 does not natively support setting different automatic replies for aliases; it only sends the primary mailbox's automatic reply regardless of the alias used.
Before you start

Ensure you have administrator privileges in the Microsoft 365 Admin Center, as implementing the most effective workarounds requires creating shared mailboxes or configuring Exchange mail-flow rules.

Solution 1Recommended

Workaround: Use a Shared Mailbox Instead of an Alias

Since Microsoft 365 does not natively support alias-specific auto-replies, converting the alias into a shared mailbox is the most reliable way to achieve this functionality.

A shared mailbox functions independently of your primary mailbox, meaning it can have its own distinct out-of-office message without requiring an extra user license.

1
Remove the existing alias

Go to the Microsoft 365 Admin Center, navigate to Users > Active users, select your account, and remove the alias you want to use for auto-replies.

2
Create a Shared Mailbox

Navigate to Teams & groups > Shared mailboxes and click 'Add a shared mailbox'. Use the exact email address you just removed as the alias.

3
Assign permissions

Select the newly created shared mailbox, click 'Edit' under Members, and add your primary account so you can view its emails.

4
Set the Automatic Reply

Open Outlook on the web, click your profile picture, select 'Open another mailbox', and enter the shared mailbox address. Then, go to Settings > Mail > Automatic replies and configure your desired message.

Workaround: Use a Shared Mailbox Instead of an Alias
Free Microsoft Office alternative

Boost Your Productivity with WPS Office

While complex server-side email configurations require Microsoft 365 Admin access, you don't need expensive subscriptions for your daily document tasks. WPS Office provides a lightweight, comprehensive, and free office suite that integrates Word, Excel, PowerPoint, and PDF editing in one single app.

  1. 1. Visit the WPS Website: Go to the official WPS Office website to find the free download link.
  2. 2. Download and Install: Download the installer for your operating system and follow the quick installation prompts.
  3. 3. Open and Create: Launch WPS Office and immediately start working with your existing Microsoft Office files without any compatibility issues.
100% compatible with Microsoft Office formats (.docx, .xlsx, .pptx)Lightweight software that runs smoothly on Windows, Mac, Linux, iOS, and AndroidBuilt-in PDF toolkit for editing, converting, and merging documentsFamiliar tabbed interface makes migrating from Microsoft Office seamless
microsoft office alternative - wps office

Frequently Asked Questions

Why can't I set an automatic reply for my Microsoft 365 alias natively in Outlook?

Microsoft Exchange treats an alias as just an alternative name for the primary mailbox. When an email arrives, Exchange resolves it to the primary account before applying any rules, meaning Outlook cannot natively distinguish between the primary address and the alias for out-of-office replies.

Is a shared mailbox free in Microsoft 365?

Yes, shared mailboxes do not require a separate user license as long as they are accessed by users who already have a valid Microsoft 365 license. They are the best free workaround for alias-specific auto-replies.

Can I use a client-side Outlook rule to reply to emails sent to an alias?

While you can attempt to create an Outlook rule stating 'have server reply using a specific message' when your alias is in the 'To' box, it often fails because Exchange automatically strips the alias address and replaces it with the primary address during routing.