如何在Azure DevOps中配置或修改发件人邮箱地址？

Got it, let's sort out this Azure DevOps email sender problem for you. The anonymous Microsoft ID getting blocked is a common headache, and switching to your organization's internal email address is totally doable—here's exactly how to make it happen:

First, a quick prerequisite: you'll need Project Collection Administrator permissions for your Azure DevOps organization, plus all the details for your company's internal SMTP server (server address, port, encryption type, and a valid email account from your org that can send via this server).

Step-by-Step Configuration #

1. Access Organization Settings
   Log into your Azure DevOps organization (e.g., https://dev.azure.com/[YourOrgName]), then click the gear icon in the top right corner to open Organization settings.

2. Navigate to Email Settings
   In the left sidebar, expand the Notifications section, then select Email settings.

3. Switch to Custom SMTP Mode
   On the Email settings page, look for the Email delivery section. By default, Azure DevOps uses Microsoft's managed email service—you'll need to select the Custom SMTP server option to use your org's email.

4. Fill in Your SMTP Details
   Here's where you input all your org's server info:

   • SMTP server: Enter your internal SMTP server address (e.g., smtp.yourcompany.com)
   • Port: Use the port your SMTP server requires (common options: 587 for TLS, 465 for SSL, or 25 if your org allows it)
   • Encryption: Pick the matching encryption type (TLS, SSL, or None—though None isn't recommended for security)
   • Sender email address: This is the org-internal email you want to use as the sender (e.g., devops-alerts@yourcompany.com)
   • Sender display name: Optional but helpful—set a friendly name like Your Company DevOps Notifications
   • Authentication: If your SMTP server requires login, choose Basic and enter the username/password for the sender email. If anonymous relay is allowed (uncommon for secure orgs), select Anonymous.

5. Test the Configuration
   Before saving, click the Send test email button at the bottom of the page. Enter a test email address you have access to, send it, and verify that the sender shows up as your org's email (not the anonymous Microsoft ID).

6. Save and Apply
   Once the test is successful, hit the Save button. From now on, all Azure DevOps notification emails will be sent from your configured org email address, which should avoid being blocked by your organization's filters.

Quick Notes to Avoid Issues #

• Make sure your SMTP server allows Azure DevOps's IP ranges to send emails, or that the sender email account is authorized to relay through the server.
• If you're using Exchange Online/Office 365 as your SMTP server and the sender email has MFA enabled, you'll need to use an app password instead of the regular account password for authentication.
• If you run into authentication errors, double-check the username/password, port, and encryption settings—small mismatches here are the most common culprits.

内容的提问来源于stack exchange，提问作者Devops user