- Outlook.com is a free personal email service from Microsoft that doesn't scan your email for the purpose of serving you ads. Automatically file emails and share photos easily.
- Microsoft Exchange 2007 mac software, free downloads and reviews at WinSite. Free Mac Microsoft Exchange 2007 Shareware and Freeware.
- Take your business further with productivity solutions designed for small business in Office 365 and Microsoft 365 Business, with the Office apps, collaboration tools and security features to help run and grow your business.
- 2017-10-19 If you are using outlook 2011 for Mac, please this link to import Entourage items to outlook 2011 for Mac. If you are using outlook 2016 for Mac, you need to do a two-step process: First, import your Entourage data into Outlook 2011 for Mac as above link. Once that's done, import from Outlook 2011 to Outlook 2016 for Mac.
We no longer offer Microsoft Exchange mailboxes but have left this tutorial here for existing exchange users. You can set up a Mac to connect to a Microsoft Exchange mailbox by using the Mac Mail email client. We have separate guides for setting up a Standard or Advanced mailbox in Mac Mail. May 20, 2019 Configure the Exchange server to support Compatible mode by using the instructions from KB article 980436. This allows the Outlook for Mac client to establish a connection by using the SSL protocol and then renegotiate by using TLS. This method allows Outlook for Mac to connect to the server even when SSL 2.0 and 3.0 are blocked.
-->Before you install Exchange Server 2019, we recommend that you review this topic to ensure your network, hardware, software, clients, and other elements meet the requirements for Exchange 2019. Also, make sure you understand the coexistence scenarios that are supported for Exchange 2019 and earlier versions of Exchange.
To actually install Exchange 2019, see Deploy new installations of Exchange.
Supported coexistence scenarios for Exchange 2019
The supported coexistence scenarios between Exchange 2019 and earlier versions of Exchange are described in the following table:
| Exchange version | Exchange 2019 organization coexistence |
|---|---|
| Exchange 2010 and earlier versions | Not supported |
| Exchange 2013 | Supported with Exchange 2013 Cumulative Update 21 (CU21) or later on all Exchange 2013 servers in the organization, including Edge Transport servers. |
| Exchange 2016 | Supported with Exchange 2016 CU11 or later on all Exchange 2016 servers in the organization, including Edge Transport servers. |
| Mixed Exchange 2013 and Exchange 2016 organization | Supported if all Exchange 2013 and Exchange 2016 servers in the organization meet the requirements as previously described in this table. |
Supported hybrid deployment scenarios for Exchange 2019
Exchange 2019 supports hybrid deployments with Office 365 tenants that have been upgraded to the latest version of Office 365. For more information about specific hybrid deployments, see Hybrid deployment prerequisites.
Network and directory server requirements for Exchange 2019
The requirements for the network and the directory servers in your Exchange 2019 organization are described in the following table:
| Component | Requirement |
|---|---|
| Domain controllers | All domain controllers in the forest need to be running one of the following versions of Windows Server: • Windows Server 2019 Standard or Datacenter • Windows Server 2016 Standard or Datacenter • Windows Server 2012 R2 Standard or Datacenter |
| Active Directory forest | The Active Directory forest functional level is Windows Server 2012 R2 or higher. |
| Active Directory site | The Active Directory site where you install the Exchange Server must contain at least one writeable domain controller that's also a global catalog server, or the installation will fail. Furthermore, you can't install the Exchange server and then remove the domain controller from the Active Directory site. |
| DNS namespace | Exchange 2019 supports the following DNS namespaces: • Contiguous • Noncontiguous • Single label domains • Disjoint For more information about DNS namespaces that are supported by Exchange, see KB2269838. |
| IPv6 | Exchange 2013 and later support IPv6 only when IPv4 is also installed and enabled on the Exchange server. If you deploy Exchange in this configuration, and your network supports IPv4 and IPv6, all Exchange servers can send data to and receive data from devices, servers, and clients that use IPv6 addresses. For more information, see IPv6 Support in Exchange 2013. |
Directory server architecture for Exchange 2019
Active Directory domain controllers on 64-bit hardware with a 64-bit version of Windows Server will increase directory service performance for Exchange 2019.
Installing Exchange 2019 on directory servers
For security and performance reasons, we don't recommend installing Exchange 2019 on Active Directory directory servers. Only install Exchange 2019 on member servers.
To learn more about the issues that you'll encounter when you install Exchange on a directory server, see Installing Exchange on a domain controller is not recommended [WarningInstallExchangeRolesOnDomainController]. After Exchange is installed, changing the server role from a member server to a directory server or vice-versa isn't supported.
Hardware requirements for Exchange 2019
For information about deploying Exchange in a virtualized environment, see Exchange Server virtualization.
| Component | Requirement | Notes |
|---|---|---|
| Processor | Either of the following types of 64-bit processors: • Intel processor that supports Intel 64 architecture (formerly known as Intel EM64T). • AMD processor that supports the AMD64 platform. Notes: • Intel Itanium IA64 processors are not supported. • Recommended supported processor sockets is up to 2 on physical machines. | See the Supported operating systems for Exchange 2019 section later in this topic for supported operating systems. |
| Memory | Varies by Exchange server role: • Mailbox: 128 GB minimum recommended • Edge Transport: 64 GB minimum recommended. | Exchange 2019 has large memory support (up to 256 GB). |
| Paging file size | Set the paging file minimum and maximum value to the same size: 25% of installed memory. | None |
| Disk space | • At least 30 GB of free space on the drive where you're installing Exchange. • At least 200 MB of free space on the system drive. • At least 500 MB of free space on the drive that contains the message queue database. | None |
| Screen resolution | 1024 x 768 pixels (XGA) or higher | None |
| File system | NTFS: Required on partitions that contain the following types of files: • The System partition. • Exchange binaries. • Files generated by Exchange diagnostic logging. • Transport database files (for example, the mail queue database). ReFS: Supported on partitions that contain the following types of Exchange files: • Mailbox databases. • Transaction logs. | None |
Supported operating systems for Exchange 2019
| Exchange component | Requirement |
|---|---|
| Mailbox and Edge Transport server roles | Windows Server 2019 Standard or Datacenter |
| Management tools | One of the following versions of Windows: • Windows Server 2019 Standard or Datacenter • 64-bit edition of Windows 10 |
Notes:
Installing Exchange 2019 on a computer that's running Windows Server Core is fully supported and recommended. The Desktop Experience feature is no longer required.
Installing Exchange 2019 on a computer that's running Nano Server isn't supported.
Supported Powershell versions for Exchange 2019 servers
Exchange 2019 servers support the version of PowerShell that's included in the release of Windows Server where Exchange is installed. Don't install stand-alone downloads of WMF or PowerShell on Exchange servers.
Installing other software on Exchange 2019 servers
We don't support installing Office client or Office server software on Exchange servers (for example, SharePoint Server, Skype for Business Server, Office Online Server, or Project Server). Other software that you want to install on an Exchange 2019 server needs to be designed to run on the same computer as Exchange Server.
Supported .NET Framework versions for Exchange 2019
We strongly recommend that you use the latest version of the .NET Framework that's supported by the release of Exchange you're installing.
Important
• Releases of .NET Framework that aren't listed in the table below aren't supported on any release of Exchange 2019. This includes minor and patch-level releases of .NET Framework.
• The complete prerequisite list for Exchange 2019 is available here.
| Exchange 2019 version | .NET Framework 4.8 | .NET Framework 4.7.2 |
|---|---|---|
| CU4, CU5 | Supported | |
| CU2, CU3 | Supported | Supported |
| RTM, CU1 | Supported |
Supported clients (with latest updates) in Exchange 2019
Office 365 ProPlus
Outlook 2019
Outlook 2016
Outlook 2013
Outlook for Mac for Office 365
Outlook 2016 for Mac
Important
You need KB3140245 to apply registry keys to enable TLS 1.1 & 1.2 support for Windows 7. Otherwise, Outlook 2013 and 2016 will not work on Windows 7.
Lync/Skype For Business Server integration with Exchange 2019
If you're integrating Lync presence and instant messaging with Exchange Server, Lync Server 2013 Cumulative Update 10 or later is required. If you're integrating Skype for Business presence and instant messaging with Exchange Server, Skype for Business Server Cumulative Update 7 or later is required.
Before you install Exchange Server 2016, we recommend that you review this topic to ensure your network, hardware, software, clients, and other elements meet the requirements for Exchange 2016. Also, make sure you understand the coexistence scenarios that are supported for Exchange 2016 and earlier versions of Exchange.
To actually install Exchange 2016, see Deploy new installations of Exchange.
Supported coexistence scenarios for Exchange 2016
The following table lists the scenarios in which coexistence between Exchange 2016 and earlier versions of Exchange is supported.
| Exchange version | Exchange organization coexistence |
|---|---|
| Exchange 2007 and earlier versions | Not supported |
| Exchange 2010 | Supported with Update Rollup 11 for Exchange 2010 SP3 or later on all Exchange 2010 servers in the organization, including Edge Transport servers. |
| Exchange 2013 | Supported with Exchange 2013 Cumulative Update 10 or later on all Exchange 2013 servers in the organization, including Edge Transport servers. |
| Mixed Exchange 2010 and Exchange 2013 organization | Supported with the following minimum versions of Exchange: • Update Rollup 11 Exchange 2010 SP3 or later on all Exchange 2010 servers in the organization, including Edge Transport servers. • Exchange 2013 Cumulative Update 10 or later on all Exchange 2013 servers in the organization, including Edge Transport servers. |
Supported hybrid deployment scenarios for Exchange 2016
Exchange 2016 supports hybrid deployments with Office 365 tenants that have been upgraded to the latest version of Office 365. For more information about specific hybrid deployments, see Hybrid Deployment Prerequisites.
Network and directory server requirements for Exchange 2016
The following table lists the requirements for the network and the directory servers in your Exchange 2016 organization.
| Component | Requirement |
|---|---|
| Domain controllers | All domain controllers in the forest need to be running one of the following versions of Windows Server: • Windows Server 2019 Standard or Datacenter • Windows Server 2016 Standard or Datacenter • Windows Server 2012 R2 Standard or Datacenter • Windows Server 2012 Standard or Datacenter • Windows Server 2008 R2 Standard or Enterprise • Windows Server 2008 R2 Datacenter RTM or later |
| Active Directory forest | The Active Directory forest functional level is Windows Server 2008 R2 or higher. |
| Active Directory site | • The Active Directory site where you install the Exchange Server must contain at least one writeable domain controller that's also a global catalog server, or the installation will fail. • You can't install the Exchange server and then remove the domain controller from the Active Directory site. |
| DNS namespace support | Exchange 2016 supports the following domain name system (DNS) namespaces: • Contiguous • Noncontiguous • Single label domains • Disjoint For more information about DNS namespaces supported by Exchange, see Microsoft Knowledge Base article 2269838, Microsoft Exchange compatibility with Single Label Domains, Disjoined Namespaces, and Discontiguous Namespaces. |
| IPv6 support | In Exchange 2016, IPv6 is supported only when IPv4 is also installed and enabled. If Exchange 2016 is deployed in this configuration, and the network supports IPv4 and IPv6, all Exchange servers can send data to and receive data from devices, servers, and clients that use IPv6 addresses. For more information, see IPv6 Support in Exchange 2013. |
Directory server architecture for Exchange 2016
Microsoft Exchange For Mac Free Trial
The use of 64-bit Active Directory domain controllers increases directory service performance for Exchange 2016.
Note
In multi-domain environments, on Windows Server 2008 domain controllers that have the Active Directory language locale set to Japanese (ja-jp), your servers may not receive some attributes that are stored on an object during inbound replication. For more information, see KB949189.
Installing Exchange 2016 on directory servers
For security and performance reasons, we recommend that you install Exchange 2016 only on member servers and not on Active Directory directory servers. To learn about the issues you can face when installing Exchange 2016 on a directory server, see Installing Exchange on a domain controller is not recommended [WarningInstallExchangeRolesOnDomainController]. After Exchange 2016 is installed, changing its role from a member server to a directory server, or vice versa, isn't supported.
Hardware requirements for Exchange 2016
For information about deploying Exchange in a virtualized environment, see Exchange Server virtualization.
| Component | Requirement | Notes |
|---|---|---|
| Processor | Either of the following types of 64-bit processors: • Intel processor that supports Intel 64 architecture (formerly known as Intel EM64T). • AMD processor that supports the AMD64 platform. Note: Intel Itanium IA64 processors are not supported. | For more information, see Sizing Exchange 2016 Deployments. See the Supported operating systems for Exchange 2016 section later in this topic for supported operating systems. |
| Memory | Varies by Exchange server role: • Mailbox: 8 GB minimum. • Edge Transport: 4 GB minimum. | For more information, see Sizing Exchange 2016 Deployments. |
| Paging file size | Set the paging file minimum and maximum value to the same size: • Less than 32 GB of RAM installed: Physical RAM plus 10MB, up to a maximum value of 32GB (32,778MB). • 32 GB of RAM or more installed: 32GB | None |
| Disk space | • At least 30 GB of free space on the drive where you're installing Exchange, plus an additional 500 MB for each Unified Messaging (UM) language pack that you plan to install. • At least 200 MB of free space on the System drive. • At least 500 MB of free space on the drive that contains the message queue database. | For more information, see Sizing Exchange 2016 Deployments. |
| Drive | DVD-ROM drive, local or network accessible. | None |
| Screen resolution | 1024 x 768 pixels (XGA) or higher | None |
| File format | NTFS: Required on partitions that contain the following types of files: • The System partition. • Exchange binaries. • Files generated by Exchange diagnostic logging. • Transport database files (for example, the mail queue database). ReFS: Supported on partitions that contain the following types of Exchange files: • Mailbox databases. • Transaction logs. • Content indexing files. | None |
Supported operating systems for Exchange 2016
Important: We don't support the installation of Exchange 2016 on a computer that's running Windows Server Core or Nano Server. The Windows Server Desktop Experience feature needs to be installed. To install Exchange 2016, you need to do one of the following to install the Desktop Experience on Windows Server prior to starting Exchange 2016 Setup:
Windows Server 2012 and Windows Server 2012 R2: Run the following command in Windows PowerShell
Windows Server 2016: Install Windows Server 2016 and choose the Desktop Experience installation option. If a computer is running Windows Server 2016 Core mode and you want to install Exchange 2016 on it, you'll need to reinstall the operating system and choose the Desktop Experience installation option.
| Component | Requirement |
|---|---|
| Mailbox and Edge Transport server roles | • Windows Server 2016 Standard or Datacenter* • Windows Server 2012 R2 Standard or Datacenter • Windows Server 2012 Standard or Datacenter |
| Management tools | One of the following versions of Windows: • Windows Server 2016 Standard or Datacenter* • Windows Server 2012 R2 Standard or Datacenter • Windows Server 2012 Standard or Datacenter • 64-bit edition of Windows 10 • 64-bit edition of Windows 8.1 |
* Requires Exchange Server 2016 Cumulative Update 3 or later.
Supported Windows Management Framework versions for Exchange 2016
Exchange 2016 only supports the version of Windows Management Framework that's built in to the release of Windows that you're installing Exchange on. Don't install versions of Windows Management Framework that are made available as stand-alone downloads on servers running Exchange.
Installing other software on Exchange 2016 servers
We don't support installing Office clients or other Office server products (for example, SharePoint Server, Skype for Business Server, Office Online Server, or Project Server) on Exchange 2016 servers. Software that you want to install on an Exchange 2016 server needs to be designed to run on the same computer as Exchange Server.
Supported .NET Framework versions for Exchange 2016
We strongly recommend that you use the latest version of .NET Framework that's supported by the release of Exchange you're installing.
Important
• Releases of .NET Framework that aren't listed in the table below are not supported on any release of Exchange 2016. This includes minor and patch-level releases of .NET Framework.
• The complete prerequisite list for Exchange 2016 is available here.
| Exchange 2016 version | .NET Framework 4.8 | .NET Framework 4.7.2 | .NET Framework 4.7.1 | .NET Framework 4.6.2 |
|---|---|---|---|---|
| CU15, CU16 | Supported | |||
| CU13, CU14 | Supported | Supported | ||
| CU11, CU12 | Supported | Supported | ||
| CU10 | Supported | |||
| CU8, CU9 | Supported | Supported | ||
| CU5, CU6, CU7 | Supported |
Note: For older versions, see Exchange Server supportability matrix.
Supported clients (with latest updates) in Exchange 2016
Office 365 ProPlus
Outlook 2019
Outlook 2016
Outlook 2013
Outlook 2010 SP2
Outlook 2016 for Mac
Outlook for Mac for Office 365
Exchange third-party clients
Exchange Server offers several well-known protocols, and publishes APIs that third-party vendors often write clients for.
Microsoft makes no warranties, expressed or implied, as to the overall suitability, fitness, compatibility, or security of clients that are created by third-party developers.
If you want to use a third-party client that uses our protocols or APIs, we recommend that you thoroughly review and test all considerations (functionality, security, maintenance, management, and so on) before you deploy the client in the enterprise workspace. We also recommend that you make sure that the third-party vendor offers an appropriate Enterprise Support Agreement (ESA).
-->Find out about the most common types of applications that you can create by using EWS in Exchange.
The EWS and Exchange architecture provides a uniform development model that you can use to create the most common types of applications in a consistent way, including the following:
Client applications — Standalone applications that use EWS to access Exchange data. Outlook and Outlook Web App are examples of client applications.
Portal applications — Applications that extend an existing web page by including information retrieved from Exchange, such as free/busy or contact information. A SharePoint web part that retrieves Exchange data is an example of a portal application.
Service applications — Background jobs used to integrate or synchronize data from Exchange into an existing system. For example, an application that synchronizes contact information from Exchange into a CRM application.
Exchange Url
Each of these application models can use a common code base to retrieve information from Exchange - so you don't need to change the EWS code used to retrieve item information between a client, portal, or service application. What might change from one application to the next is the mailbox access and authentication mechanism. For example, client applications commonly use direct user access and basic or NTLM authentication, whereas a service application likely uses impersonation for mailbox access and OAuth authentication.
Client applications
An EWS client application is any standalone application that uses EWS to retrieve information from the Exchange store. EWS client applications use direct client access or delegate access to retrieve data from the mailbox store. The following are some examples of client applications that use EWS:
Outlook, in features such as MailTips, availability, and user OOF status
OWA for Devices
Outlook for Mac 2011
Lync, for availability information
Client applications commonly use direct access and basic or NTLM authentication, so that users are limited to accessing information in their own mailbox with their own logon credentials. Client applications should also support delegate access for users who have been given permission to access another user's mailbox.
Portal applications
A portal application extends an existing web page or portal to include Exchange mailbox information as a personalized component of the page. SharePoint web parts are the most common portal applications and provide users with a personalized experience by providing views into Exchange mailbox data, such as unread messages, most recent messages, and calendar events, alongside their commonly viewed SharePoint portal page. EWS portal applications can use direct client access, delegate access, or impersonation to retrieve data from the mailbox store. Because Exchange 2013 and SharePoint 2013 both support the OAuth authorization protocol for server-to-server authentication, OAuth provides the most seamless and secure authentication method.
Service applications
A service application is usually a background job built into an existing application that extends to Exchange to correlate data between the system and the Exchange store. Service applications typically do not have a user interface and use impersonation or OAuth for authentication and access. Creating a service account to impersonate users is common in EWS service apps because you can grant a single account permission to impersonate a set of users and perform mailbox operations for those accounts. For example, an EWS service application can synchronize data between marketing lists in a CRM solution and Exchange distribution groups by using a service account and impersonation.