Skip to main content

Microsoft Exchange Online

Email integration

Connect NIM with Microsoft Exchange Online to automate data synchronization and operational workflows across your environment.

Solutions This Integration SolvesDirect link to Solutions This Integration Solves

User provisioning

Maintain supported user and account records through NIM.

  • Keeps service identities current
  • Reduces manual setup

Service access management

Manage supported groups, roles, and relationships consistently.

  • Improves access governance
  • Supports audit readiness

Communication readiness

Keep people and related service data aligned with your identity source.

  • Improves operational accuracy
  • Reduces service disruption

Service automation

Standardize common administrative tasks for communication systems.

  • Faster response times
  • Repeatable execution

GuidesDirect link to Guides

Configure ConnectionReview setup steps, required settings, and implementation details.

Connector repository

Browse the Microsoft Exchange Online connector repository on GitHub.

Supported operationsDirect link to Supported operations

Filter tables by supported operation

Showing 6 of 6 tables
TableReadCreateUpdateDelete
CASMailboxes
DistributionGroup
DistributionGroupMembers
MailboxAutoReplyConfigurations
Mailboxes
MailboxPermissions

TroubleshootingDirect link to Troubleshooting

Problem

TLS protocol error during an Exchange Online connection

Example error

The underlying connection was closed: An unexpected error occurred on a receive. The specified value is not valid in the 'SslProtocolType' enumeration. Parameter name: sslProtocolType.

Likely cause

The Windows or .NET Framework TLS configuration used by the connection does not support the requested protocol.

Resolution

  1. Check whether TLS 1.2 is enabled for the Windows client and the .NET Framework used by the connector.
  2. Review the registry examples below against the server's current settings and your organization's TLS policy. Back up the affected keys before changing them.
  3. After applying approved changes, restart the affected process and test the Exchange Online connection again.

Registry settings to reviewDirect link to Registry settings to review

The following values are grouped by Windows component. They are examples to compare with the server's configuration; apply only the changes needed for the affected component. See Microsoft's guidance for Schannel TLS settings, .NET Framework TLS defaults, and WinHTTP secure protocols.

Schannel: disable TLS 1.0 and 1.1, enable TLS 1.2Direct link to Schannel: disable TLS 1.0 and 1.1, enable TLS 1.2

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client]
"DisabledByDefault"=dword:00000001
"Enabled"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client]
"DisabledByDefault"=dword:00000001
"Enabled"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server]
"DisabledByDefault"=dword:00000001
"Enabled"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001

.NET Framework: use system TLS defaultsDirect link to .NET Framework: use system TLS defaults

The v2.0.50727 keys apply to .NET Framework 2.0 and 3.5; the v4.0.30319 keys apply to .NET Framework 4.x. Both 64-bit and 32-bit registry paths are shown.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001

WinHTTP: allow TLS 1.2 by defaultDirect link to WinHTTP: allow TLS 1.2 by default

The DefaultSecureProtocols value 0x00000800 represents TLS 1.2 for WinHTTP applications that use this default. Both registry paths are shown for a 64-bit server.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp]
"DefaultSecureProtocols"=dword:00000800

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp]
"DefaultSecureProtocols"=dword:00000800
Last updated on