1. Outlook 365 Office
2. Outlook 365 Georgia Email
3. Outlook 3660
4. Outlook 365 Office Mail
5. Outlook 365 Sign In
6. Outlook 3660

Important: If you have a Microsoft Microsoft 365 account, and you use Outlook and Outlook on the web or Outlook on the web for business, you need to create a signature in both products. To create and use email signatures in Outlook on the web, see Create.

1. Microsoft Office 365 at CCU. Microsoft Office 365 is a cloud-based service that provides a single platform for Coastal Carolina University email, and for students, faculty and staff to access the latest versions of Microsoft Office (Word, Excel, PowerPoint, OneNote) for Windows and OS X, and to get cloud-based mobile apps to access and edit files online including PC, Mac, iPad, iPhone and Android.
2. A Microsoft 365 subscription includes premium Outlook features like an ad-free interface, custom domains, enhanced security, the full desktop version of Office apps, and 1 TB of cloud storage.
3. Microsoft 365 with Office apps Microsoft 365 Introducing Microsoft Viva, the new employee experience platform designed to help people connect, focus, learn, and thrive at work.
4. Starting on November 1, 2021, the following versions are the minimum versions of Outlook for Windows you need to be using to be able to connect to Microsoft 365 services, such as Exchange Online. Version 1706 of Microsoft 365 Apps. Version 16.0.4600.1000 of Office.

The Teams Meeting add-in lets users schedule a Teams meeting from Outlook. The add-in is available for Outlook on Windows, Mac, web, and mobile.

Teams Meeting add-in in Outlook for Windows

The Teams Meeting add-in is automatically installed for users who have Microsoft Teams and either Office 2013, Office 2016, or Office 2019 installed on their Windows PC. Users will see the Teams Meeting add-in on the Outlook Calendar ribbon.

Note

• There is no direct URL that links to the Teams add-in.
• There are additional considerations if your organization runs both Teams and Skype for Business. Under some circumstances, the Teams add-in is not available in Outlook. See Upgrade from Skype for Business to Teams for details.
• User permissions to execute the Regsvr32.exe file is a minimum requirement for the Teams Meeting add-in to be installed on the computer.
• If users do not see the Teams Meeting add-in, instruct them to close Outlook and Teams, then restart the Teams client first, then sign in to Teams, and then restart the Outlook client, in that specific order.
• If you are using an Office Outlook installation from the Microsoft Store, the Teams Meeting add-in isn't supported. Users who require this add-in are advised to install Click-to-Run version of Office, as outlined in Office on Windows 10 in S mode article.

Teams Meeting add-in in Outlook for Mac

The Teams Meeting button in Outlook for Mac will appear in the Outlook for Mac ribbon if Outlook is running production build 16.24.414.0 and later and is activated with a Microsoft 365 or Office 365 client subscription.​

The meeting coordinates (the Teams join link and dial-in numbers) will be added to the meeting invite after the user clicks Send.

Teams Meeting add-in in Outlook Web App

The Teams Meetings button in Outlook Web App will appear as part of new event creation if the user is on an early version of the new Outlook on the web. See the Outlook Blog to learn about how users can try the early version of the new Outlook on the web.

The meeting coordinates (the Teams join link and dial-in numbers) will be added to the meeting invite after the user clicks Send.

Teams Meeting add-in in Outlook mobile (iOS and Android)

The Teams Meeting button shows up in latest builds of the Outlook iOS and Android app.

The meeting coordinates (the Teams join link and dial-in numbers) will be added to the meeting invite after the user clicks Send.

Teams Meeting add-in and FindTime for Outlook

FindTime is an add-in for Outlook that helps users reach consensus on a meeting time across companies. Once the meeting invitees have provided their preferred times, FindTime sends out the meeting invite on the user's behalf. If the Online meeting option is selected in FindTime, FindTime will schedule a Skype for Business or Microsoft Teams meeting. (FindTime will use whichever has been set by your organization as the default online meeting channel.)

Note

If you saved a Skype for Business setting in your Findtime dashboard, FindTime will use that instead of Microsoft Teams. If you want to use Microsoft Teams, delete the Skype for Business setting in your dashboard.

For more information, see Schedule meetings with FindTime.

Authentication requirements

The Teams Meeting add-in requires users to sign in to Teams using Modern Authentication. If users do not use this method to sign in, they'll still be able to use the Teams client, but will be unable to schedule Teams online meetings using the Outlook add-in. You can fix this by doing one of the following:

• If Modern Authentication is not configured for your organization, you should configure Modern Authentication.
• If Modern Authentication is configured, but they canceled out on the dialog box, you should instruct users to sign in again using multi-factor authentication.

To learn more about how to configure authentication, see Identity models and authentication in Microsoft Teams.

Enable private meetings

Allow scheduling for private meetings must be enabled in the Microsoft Teams admin center for the add-in to get deployed. In the admin center, go to Meetings > Meeting Policies, and in the General section, toggle Allow scheduling private meetings to On.)

The Teams client installs the correct add-in by determining if users need the 32-bit or 64-bit version.

Note

Users might need to restart Outlook after an installation or upgrade of Teams to get the latest add-in.​

Teams upgrade policy and the Teams Meeting add-in for Outlook

Customers can choose their upgrade journey from Skype for Business to Teams. Tenant admins can use the Teams co-existence mode to define this journey for their users. Tenant admins have the option to enable users to use Teams alongside Skype for Business (Islands mode).

When users who are in Island mode schedule a meeting in Outlook, they typically expect to be able to choose whether to schedule a Skype for Business or a Teams meeting. In Outlook on the web, Outlook Windows, and Outlook Mac, users see both Skype for Business and Teams add-ins when in Islands mode by default. You can configure a Teams meeting policy setting to control whether users in Islands mode can only use the Teams Meeting add-in or both the Teams Meeting and Skype for Business Meeting add-ins.

Due to certain limitations in the initial release, Outlook mobile can only support creating Skype for Business or Teams meetings. See the following table for details.

Set whether users in Islands mode can only use the Teams Meeting add-in or both the Teams Meeting and Skype for Business Meeting add-ins

As an admin, you can configure a Teams meeting policy setting to control which Outlook meeting add-in is used for users who are in Islands mode. You can specify whether users can only use the Teams Meeting add-in or both the Teams Meeting and Skype for Business Meeting add-ins to schedule meetings in Outlook.

You can only apply this policy to users who are in Islands mode and have the AllowOutlookAddIn parameter set to True in their Teams meeting policy. For steps on how to set this policy, see Meeting policy settings - General.

Other considerations

The Teams Meeting add-in is still building functionality, so be aware of the following:

• The Teams Meeting add-in requires an Exchange mailbox for the primary user scheduling the meeting. Ensure that you have at least one Exchange mailbox configured in your Outlook profile and use it to schedule Teams meetings with the add-in. For Exchange requirements, see How Exchange and Teams interact.
• The add-in is for scheduled meetings with specific participants, not for meetings in a channel. Channel meetings must be scheduled from within Teams.
• The add-in will not work if an Authentication Proxy is in the network path of the user's PC and Teams Services.
• Users can't schedule live events from within Outlook. Go to Teams to schedule live events. For more information, see What are Microsoft Teams live events?.

Learn more about meetings and calling in Microsoft Teams.

Troubleshooting

Use the following steps to troubleshoot issues with the Teams Meeting add-in.

Teams Meeting add-in in Outlook for Windows does not show

If you cannot get the Teams Meeting add-in for Outlook to install, try these troubleshooting steps.

Download and run the Microsoft Support Recovery Assistant to perform automated troubleshooting steps and fixes.

Alternatively, perform the following steps manually:

• Windows 7 users must install the Update for Universal C Runtime in Windows for the Teams Meeting add-in to work.
• Check that the user has a Teams Upgrade policy which enables scheduling meetings in Teams. See Upgrade from Skype for Business to Teams for more details.
• Check that the user has a Teams Meeting policy that permits the Outlook Add-in. See Meeting policy settings - General for more details.
• Ensure the user has the Teams desktop client installed. The meeting add-in will not be installed when only using the Teams web client.
• Ensure the user has Outlook 2013 or later installed.
• Make sure the user has permission to execute regsvr32.exe.
• Ensure that all available updates for Outlook desktop client have been applied.
• Follow these steps:
  • Restart the Teams desktop client.
  • Sign out and then sign back in to the Teams desktop client.
  • Restart the Outlook desktop client. (Make sure Outlook isn't running in admin mode.)

If you still don't see the add-in, make sure that it isn't disabled in Outlook.

• In Outlook, choose File and then Options.
• Select the Add-ins tab of Outlook Options dialog box.
• Confirm that Microsoft Teams Meeting Add-in for Microsoft Office is listed in the Active Application Add-ins list
• If the Teams Meeting Add-in is listed in the Disabled Application Add-ins list, select COM Add-ins in Manage and then select Go…
• Set the checkbox next to Microsoft Teams Meeting Add-in for Microsoft Office.
• Choose OK on all dialog boxes and restart Outlook.

For general guidance about how to manage add-ins, see View, manage, and install add-ins in Office programs.

If the add-in still does not show, use the following steps to verify the registry settings.

Note

Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.

• Launch RegEdit.exe
• Navigate to HKEY_CURRENT_USERSoftwareMicrosoftOfficeOutlookAddins
• Verify TeamsAddin.FastConnect exists.
• Within TeamsAddin.FastConnect, verify LoadBehavior exists and is set to 3.
  • If LoadBehavior has a value other than 3, change it to 3 and restart Outlook.

Delegate scheduling does not work

If your administrator has configured Microsoft Exchange to control access to Exchange Web Server (EWS), a delegate won't be able to schedule a Teams meeting on behalf of the boss. The solution for this configuration is under development and will be released in the future. As a workaround, your administrator can add the following string to the EWS Allow List: 'SchedulingService'.

Related topics

Important

Mail flow rules are now available in the new Exchange Admin Center. Try it now!

Prerequisites: Office 365 or Microsoft 365 subscription, Exchange Online Plan

This article explains how you can send email from devices and business applications when all of your mailboxes are in Microsoft 365 or Office 365. For example:

• You have a scanner, and you want to email scanned documents to yourself or someone else.

• You have a line-of-business (LOB) application that manages appointments, and you want to email reminders to clients of their appointment time.

Option 1 (recommended): Authenticate your device or application directly with a Microsoft 365 or Office 365 mailbox, and send mail using SMTP AUTH client submission

Note

This option is not compatible with Microsoft Security Defaults or multi-factor authentication (MFA). If your environment uses Microsoft Security Defaults or MFA, we recommend using Option 2 or 3 below.

You must also verify that SMTP AUTH is enabled for the mailbox being used. For more information, see Enable or disable authenticated client SMTP submission (SMTP AUTH) in Exchange Online.

See Basic Authentication and Exchange Online for the latest announcements concerning this option..

This option supports most usage scenarios and it's the easiest to set up. Choose this option when:

• You want to send email from a third-party hosted application, service, or device.

• You want to send email to people inside and outside your organization.

To configure your device or application, connect directly to Microsoft 365 or Office 365 using the SMTP AUTH client submission endpoint smtp.office365.com.

Each device or application must be able to authenticate with Microsoft 365 or Office 365. The email address of the account that's used to authenticate with Microsoft 365 or Office 365 will appear as the sender of messages from the device or application.

How to set up SMTP AUTH client submission

Enter the following settings directly on your device or in the application as their guide instructs (it might use different terminology than this article). As long as your scenario meets the requirements for SMTP AUTH client submission, the following settings will enable you to send email from your device or application.

TLS and other encryption options

Determine what version of TLS your device supports by checking the device guide or with the vendor. If your device or application does not support TLS 1.2 or above:

• Use direct send (Option 2) or Microsoft 365 or Office 365 SMTP relay (Option 3) for sending mail instead (depending on your requirements).

• Use an on-premises Exchange server (or another SMTP email server) if your device is unable to meet the previous requirements for connecting to Microsoft 365 or Office 365. In fact, you might find it easier to manage multiple devices and applications that send email messages in an on-premises Exchange server instead of connecting them all to Microsoft 365 or Office 365 directly. The Exchange server would relay messages in the same way that a device would use Microsoft 365 or Office 365 to relay messages using Option 3 below. You can find out more about configuring your own email server to send emails to Microsoft 365 or Office 365 here: Set up connectors to route mail between Microsoft 365 or Office 365 and your own email servers.

Note

If your device recommends or defaults to port 465, it does not support SMTP AUTH client submission.

How SMTP AUTH client submission works

The following diagram gives you a conceptual overview of what your environment will look like.

Features of SMTP AUTH client submission

• SMTP AUTH client submission allows you to send email to people in your organization and outside your company.

• This method bypasses most spam checks for email sent to people in your organization. This can help protect your company IP addresses from being blocked by a spam list.

• With this method, you can send email from any location or IP address, including your (on-premises) organization's network, or a third-party cloud hosting service, like Microsoft Azure.

Requirements for SMTP AUTH client submission

• Authentication: You must be able to configure a username and password to send email on the device. You cannot use Microsoft Security Defaults or multi-factor authentication (MFA), which disable basic authentication and are designed to protect your users from compromise. If your environment uses Microsoft Security Defaults or MFA, we recommend using Option 2 or 3 below.

• Mailbox: You must have a licensed Microsoft 365 or Office 365 mailbox to send email from.

• Transport Layer Security (TLS): Your device must be able to use TLS version 1.2 and above.

• Port: Port 587 (recommended) or port 25 is required and must be unblocked on your network. Some network firewalls or ISPs block ports, especially port 25.

• DNS: You must use the DNS name smtp.office365.com. Do not use an IP address for the Microsoft 365 or Office 365 server, as IP Addresses are not supported.

Note

For information about TLS, see How Exchange Online uses TLS to secure email connections and for detailed technical information about how Exchange Online uses TLS with cipher suite ordering, see Enhancing mail flow security for Exchange Online.

Limitations of SMTP AUTH client submission

You can only send from one email address unless your device can store login credentials for multiple Microsoft 365 or Office 365 mailboxes. Microsoft 365 or Office 365 imposes a limit of 30 messages sent per minute, and a limit of 10,000 recipients per day.

Outlook 365 Office

Option 2: Send mail directly from your printer or application to Microsoft 365 or Office 365 (direct send)

Choose this option when:

• Your environment uses Microsoft Security Defaults or multi-factor authentication (MFA).

• SMTP client submission (Option 1) is not compatible with your business needs or with your device.

• You only need to send messages to recipients in your own organization who have mailboxes in Microsoft 365 or Office 365; you don't need to send email to people outside of your organization.

Other scenarios when direct send may be your best choice:

• You want your device or application to send from each user's email address and do not want each user's mailbox credentials configured to use SMTP client submission. Direct send allows each user in your organization to send email using their own address.

  Avoid using a single mailbox with Send As permissions for all your users. This method is not supported because of complexity and potential issues.

• You want to send bulk email or newsletters. Microsoft 365 or Office 365 does not allow you to do this via SMTP client submission. Direct send allows you to send a high volume of messages.

  Note that there is a risk of your email being marked as spam by Microsoft 365 or Office 365. You might want to enlist the help of a bulk email provider to assist you. For example, they'll help you adhere to best practices, and can help ensure that your domains and IP addresses are not blocked by others on the internet.

Settings for direct send

Outlook 365 Georgia Email

Enter the following settings on the device or in the application directly.

We recommend adding an SPF record to avoid having messages flagged as spam. If you are sending from a static IP address, add it to your SPF record in your domain registrar's DNS settings as follows:

Step-by-step instructions for direct send

1. If your device or application can send from a static public IP address, obtain this IP address and make a note of it. You can share your static IP address with other devices and users, but don't share the IP address with anyone outside of your company. Your device or application can send from a dynamic or shared IP address but messages are more prone to antispam filtering.

2. Sign in to the Microsoft 365 admin center.

3. Go to Settings > Domains, select your domain (for example, contoso.com), and find the MX record.

   The MX record will have a Points to address or value value that looks similar to contoso-com.mail.protection.outlook.com.

4. Make a note of the MX record Points to address or value value, which we refer to as your MX endpoint.

5. Go back to the device, and in the settings, under what would normally be called Server or Smart Host, enter the MX record POINTS TO ADDRESS value you recorded in step 4.

   Note

   Do NOT use an IP address for the Microsoft 365 or Office 365 server connection, as IP addresses are not supported.

6. Now that you are done configuring your device settings, go to your domain registrar's website to update your DNS records. Edit your sender policy framework (SPF) record. In the entry, include the IP address that you noted in step 1. The finished string looks similar to this:

   v=spf1 ip4:10.5.3.2 include:spf.protection.outlook.com ~all

   where 10.5.3.2 is your public IP address.

   Note

   Skipping this step might cause email to be sent to recipients' junk mail folders.

7. To test the configuration, send a test email from your device or application, and confirm that the recipient received it.

How direct send works

In the following diagram, the application or device in your organization's network uses direct send and your Microsoft 365 or Office 365 mail exchange (MX) endpoint to email recipients in your organization. It's easy to find your MX endpoint in Microsoft 365 or Office 365 if you need to look it up.

You can configure your device to send email direct to Microsoft 365 or Office 365. Use direct send to relay email to recipients with Microsoft 365 or Office 365 mailboxes in your organization. Direct send also works for external recipients with mailboxes in Microsoft 365 or Office 365. If your device uses direct send to try to relay an email for a recipient who doesn't have a Microsoft 365 or Office 365 mailbox, the email will be rejected.

Note

If your device or application has the ability to act as a email server to deliver messages to Microsoft 365 or Microsoft 365 or Office 365 as well as other email providers, there are no Microsoft 365 or Office 365 settings needed for this scenario. Consult your device or application instructions for more information.

Features of direct send

• Uses Microsoft 365 or Office 365 to send emails, but does not require a dedicated Microsoft 365 or Office 365 mailbox.

• Doesn't require your device or application to have a static IP address. However, this is recommended if possible.

• Doesn't work with a connector; never configure a device to use a connector with direct send, this can cause problems.

• Doesn't require your device to support TLS.

Direct send has higher sending limits than SMTP client submission. Senders are not bound by the 30 messages per minute or 10,000 recipients per day limit.

Requirements for direct send

• Port: Port 25 is required and must be unblocked on your network.

• Static IP address is recommended: A static IP address is recommended so that an SPF record can be created for your domain. This helps avoid your messages being flagged as spam.

• Does not require a Microsoft 365 or Office 365 mailbox with a license.

Limitations of direct send

• Direct send cannot be used to deliver email to external recipients, for example, recipients with Yahoo or Gmail addresses.

• Your messages will be subject to antispam checks.

• Sent mail might be disrupted if your IP addresses are blocked by a spam list.

• Microsoft 365 and Office 365 use throttling policies to protect the performance of the service.

Option 3: Configure a connector to send mail using Microsoft 365 or Office 365 SMTP relay

This option is more difficult to implement than the others. Only choose this option when:

• Your environment uses Microsoft Security Defaults or multi-factor authentication (MFA).

• SMTP client submission (Option 1) is not compatible with your business needs or with your device

• You can't use direct send (Option 2) because you must send email to external recipients.

SMTP relay lets Microsoft 365 or Office 365 relay emails on your behalf by using a connector that's configured with your public IP address or a TLS certificate. Setting up a connector makes this a more complicated option.

Settings for Microsoft 365 or Office 365 SMTP relay

Outlook 3660

If you already have a connector that's configured to deliver messages from your on-premises organization to Microsoft 365 or Office 365 (for example, a hybrid environment), you probably don't need to create a dedicated connector for Microsoft 365 or Office 365 SMTP relay. If you need to create a connector, use the following settings to support this scenario:

We recommend adding an SPF record to avoid having messages flagged as spam. If you are sending from a static IP address, add it to your SPF record in your domain registrar's DNS settings as follows:

Step-by-step configuration instructions for SMTP relay

1. Obtain the public (static) IP address that the device or application with send from. A dynamic IP address isn't supported or allowed. You can share your static IP address with other devices and users, but don't share the IP address with anyone outside of your company. Make a note of this IP address for later.

2. Sign in to the Microsoft 365 admin center.

3. Go to Settings > Domains, select your domain (for example, contoso.com), and find the MX record.

   The MX record will have a Points to address or value value that looks similar to contoso-com.mail.protection.outlook.com.

4. Make a note of the MX record Points to address or value value, which we refer to as your MX endpoint.

5. Check that the domains that the application or device will send to have been verified. If the domain is not verified, emails could be lost, and you won't be able to track them with the Exchange Online message trace tool.

6. In Microsoft 365 or Office 365, select Admin and then Exchange to go to the Exchange admin center.

7. In the Exchange admin center, go to Mail flow > Connectors.

8. Check the list of connectors set up for your organization. If there is no connector listed from your organization's email server to Microsoft 365 or Office 365, create one:

   a. To start the wizard, click the plus symbol +.

   b. On the first screen, choose the options that are depicted in the following screenshot:

   c. Click Next, and give the connector a name.

   d. On the next screen, choose the option By verifying that the IP address of the sending server matches one of these IP addresses that belong to your organization, and add the IP address from step 1.

   e. Leave all the other fields with their default values, and select Save.

9. Now that you are done with configuring your Microsoft 365 or Office 365 settings, go to your domain registrar's website to update your DNS records. Edit your SPF record. Include the IP address that you noted in step 1. The finished string should look similar to this v=spf1 ip4:10.5.3.2 include:spf.protection.outlook.com ~all, where 10.5.3.2 is your public IP address. Skipping this step can cause email to be sent to recipients' junk mail folders.

10. Now, go back to the device, and in the settings, find the entry for Server or Smart Host, and enter the MX record POINTS TO ADDRESS value that you recorded in step 3.

11. To test the configuration, send a test email from your device or application, and confirm that it was received by the recipient.

Configure a certificate-based connector to relay email through Microsoft 365 or Office 365

If your devices or applications are capable of using a certificate for mail flow, you can configure a certificate-based connector to relay email through Microsoft 365 or Office 365.

To do this, verify the subject name on the certificate used by the sending device or application. The common name (CN) or subject alternative name (SAN) in the certificate should contain a domain name that you have registered in Microsoft 365 or Office 365. Also, you must create a certificate-based connector in Microsoft 365 or Office 365 with this same domain name to accept and relay emails coming from these devices, applications, or any other on-premises server. For more information about this method, see important notice for email customers who have configured connectors.

How Microsoft 365 or Office 365 SMTP relay works

Outlook 365 Office Mail

In the following diagram, the application or device in your organization's network uses a connector for SMTP relay to email recipients in your organization.

• The Microsoft 365 or Office 365 connector that you configure authenticates your device or application with Microsoft 365 or Office 365 using an IP address. Your device or application can send email using any address (including ones that can't receive mail), as long as the address uses one of your domains. The email address doesn't need to be associated with an actual mailbox. For example, if your domain is contoso.com, you could send from an address like do_not_reply@contoso.com.

• Microsoft 365 or Office 365 SMTP relay uses a connector to authenticate the mail sent from your device or application. This allows Microsoft 365 or Office 365 to relay those messages to your own mailboxes and external recipients. Microsoft 365 or Office 365 SMTP relay is similar to direct send except that it can send mail to external recipients.

• Due to the added complexity of configuring a connector, direct send is recommended over Microsoft 365 or Office 365 SMTP relay, unless you must send email to external recipients. To send email using Microsoft 365 or Office 365 SMTP relay, your device or application server must have a static IP address or address range. You can't use SMTP relay to send email directly to Microsoft 365 or Office 365 from a third-party hosted service, such as Microsoft Azure. For more information, see Troubleshoot outbound SMTP connectivity issues in Azure.

Features of Microsoft 365 or Office 365 SMTP relay

• Microsoft 365 or Office 365 SMTP relay does not require the use of a licensed Microsoft 365 or Office 365 mailbox to send emails.

• Microsoft 365 or Office 365 SMTP relay has higher sending limits than SMTP client submission; senders are not bound by the 30 messages per minute or 10,000 recipients per day limits.

Outlook 365 Sign In

Requirements for Microsoft 365 or Office 365 SMTP relay

• Static IP address or address range: Most devices or applications are unable to use a certificate for authentication. To authenticate your device or application, use one or more static IP addresses that are not shared with another organization.

• Connector: You must set up a connector in Exchange Online for email sent from your device or application.

• Port: Port 25 is required and must not be blocked on your network or by your ISP.

• Licensing: SMTP relay doesn't use a specific Microsoft 365 or Office 365 mailbox to send email. This means that users must have their own licenses if they send email from devices or applications that are configured for SMTP relay. If you have senders who use a device or LOB application and those senders do not have Microsoft 365 or Office 365 mailbox licenses, obtain and assign an Exchange Online Protection license to each unlicensed sender. This is the least expensive license that allows you to send email via Microsoft 365 or Office 365.

Limitations of Microsoft 365 or Office 365 SMTP relay

• Sent mail can be disrupted if your IP addresses are blocked by a spam list.

• Reasonable limits are imposed for sending. For more information, see High-risk delivery pool for outbound messages.

• Requires static unshared IP addresses (unless a certificate is used).

Compare the options

Here's a comparison of each configuration option and the features they support.

Use your own email server to send email from multifunction devices and applications

Outlook 3660

If you happen to have an on-premises email server, you should seriously consider using that server for SMTP relay instead of Microsoft 365 or Office 365. A local email server that you have physical access to is much easier to configure for SMTP relay by devices and applications on your local network. The details about how to do this depend on your on-premises email server. For Exchange Server, see the following articles:

Related articles