You can send mail as an Outlook.com alias from Gmail, but the setup fails for a predictable reason. Gmail’s “Send mail as” feature authenticates over SMTP with a username and password, and Microsoft rejects the login when two-step verification is enabled on the account and you supply the regular account password. The fix is an app password, and once you have one, the whole thing takes about five minutes. This guide walks through the alias side first, then the Gmail side, with notes on Yahoo and on what changes when the mailbox lives in Microsoft 365 rather than Outlook.com.
Understand what an Outlook.com alias actually is before wiring it into Gmail
An email alias in Outlook is not a separate mailbox. It is an additional address that delivers into the same inbox as your primary address, and Outlook.com attaches aliases to a Microsoft account rather than to a standalone mailbox. That distinction matters for this project: when Gmail sends a message from the alias, the outgoing mail is authenticated against the underlying Microsoft account, not against the alias itself. The alias is a label on the envelope; the credentials belong to the account behind it.
Adding aliases is straightforward. Sign in at account.microsoft.com, open the aliases section, and add a new address on outlook.com, hotmail.com, or another Microsoft domain. Microsoft limits how frequently users can add aliases, so if you are building out several at once, expect a cooldown after a couple of additions in a short window. New aliases can take up to 24 hours to work reliably across all services, which is why a Gmail SMTP test that fails ten minutes after creation is not necessarily a broken configuration.
Two details trip people up later. First, security codes are sent to the primary username, not to the alias, so keep access to that primary address when you start experimenting. Second, plus addressing provides aliases without setup: anything sent to yourname+shopping@outlook.com lands in your inbox, and Gmail’s Send mail as accepts that full plus address as the From line. If you only need a handful of disposable sender identities, plus addressing may be all you need, and you can skip the alias creation step entirely.
Why the regular password fails and the app password works
Gmail’s Send mail as requires SMTP credentials, and Microsoft requires an app password when two-step verification is on, or Gmail rejects the login with 535 5.7.8. That error code is an authentication failure, not a network problem, and it appears even when your password is correct. Microsoft deliberately blocks basic authentication with the account password once two-step verification is active, so the credential Gmail needs is a one-off app password generated for that purpose.
Generate one at account.microsoft.com/security under advanced security options. Give it a label like “Gmail SMTP” so you can revoke it later without disturbing anything else. The password is displayed once; copy it before closing the page. If two-step verification is not enabled on the account, the regular password usually works, but enabling two-step verification is worth doing anyway, and the app password route then becomes mandatory.
Configure Gmail Send mail as with the Outlook.com SMTP settings
In Gmail, open Settings, go to the Accounts and Import tab, and click “Add another email address” under Send mail as. Enter the alias as the name and address, and leave “Treat as an alias” checked unless you want replies routed elsewhere. On the next screen, set the SMTP server to smtp-mail.outlook.com, port 587, with TLS selected. The username is the full Outlook.com address you are sending from, which can be the alias itself, and the password is the app password you just generated.
If the connection test fails, work through the obvious causes in order. Port 465 with SSL is the fallback if 587 is blocked on your network. Confirm you pasted the app password without a trailing space. Verify the alias has finished propagating, since new aliases can take up to 24 hours to work. And check that you are not trying to send from an alias in Microsoft 365 that Microsoft has not attached to the account, because the SMTP login will fail even though the From line looks valid in Gmail’s interface.
Once Gmail accepts the credentials, it sends a verification email to the alias. That message arrives in the Outlook.com inbox, so open it and click the confirmation link or paste the code into Gmail. After that, the alias appears in the From dropdown when you compose. Gmail rewrites the envelope sender to your Gmail address by default, which some recipients will see in headers; if that matters, use the alias as the reply-to or accept the mismatch as a known limitation of sending through a third-party client.
The Yahoo equivalent follows the same logic. Yahoo Mail’s sending identities feature accepts an external address and asks for SMTP credentials, which means the same app password and the same smtp-mail.outlook.com settings apply. Yahoo is stricter about verification and sometimes requires the confirmation email before it will save the identity, so have the Outlook.com inbox open in another tab. The 535 5.7.8 failure appears in Yahoo too when the wrong password type is supplied.
Things change when the mailbox is not Outlook.com but Exchange Online. Microsoft 365 adds aliases to a mailbox through the Exchange admin center or PowerShell, and an alias must use a domain added to Microsoft 365 rather than a personal outlook.com address. An administrator adds aliases in the Microsoft 365 admin center or with the Add-MailboxPermission and Set-Mailbox commands, and business plans allow roughly 300 addresses per mailbox. Sending from those aliases inside Outlook requires a separate switch: an administrator enables sending from aliases via Set-OrganizationConfig SendFromAliasEnabled in PowerShell. That setting governs the desktop and web clients, not Gmail, so a Gmail identity pointing at a Microsoft 365 mailbox still authenticates with an app password and still needs SMTP AUTH enabled on the mailbox, which many tenants disable by default.
If your goal is a shared sending address rather than a personal alias, an alias vs shared mailbox decision matters. An alias delivers to one person’s inbox and cannot be logged into separately. A shared mailbox has its own address, its own permissions, and its own send-as behavior, and it is the better fit for team addresses like support@. Aliases are for personal alternate identities; shared mailboxes are for role-based ones.
Start by deciding whether you need a true alias or whether plus addressing covers the job. If you need the alias, create it, wait out the propagation window, generate an app password, and plug the four SMTP values into Gmail or Yahoo. Keep the app password labeled and revocable, expect the 535 5.7.8 error to mean “wrong credential type” rather than “wrong password,” and test with a message to an outside address before relying on the identity for anything important. On Microsoft 365 tenants, confirm SMTP AUTH is enabled for the mailbox before you spend time debugging Gmail’s side of the connection.