Forum Discussion

Matt-Sywulak's avatar
Matt-Sywulak
Copper Contributor
Jul 29, 2024

Properties are not applicable to connector of type 'OnPremises' with the current combination.

It has come to my attention that there are new limitations on Inbound on-premise connectors. Specifically, the following options are no longer available:
• RequireTls
• RestrictDomainsToCertificate
• RestrictDomainsToIpAddresses
This change appears to be quite recent, as I'm unable to find any discussions about it online. The impact is significant - I can neither create new Inbound on-premises scoped connectors nor modify existing ones within our tenant.

Upon investigation, I discovered that Microsoft updated their documentation just four days ago. The GitHub commit (https://github.com/MicrosoftDocs/office-docs-powershell/commit/8ca7602b857e07f8d760922af0c3ca98a107c22d) indicates that these flags are now exclusively for Partner type connectors.

This change seems counterintuitive, as it prevents the creation of new connectors using the Exchange GUI or PowerShell with the recommended "Authenticating sent email" settings. These settings typically involve verifying that the subject name on the server's authentication certificate matches the specified domain.

I've attached screenshots demonstrating the inability to update existing connectors with these flags or add new ones with these settings.

Has anyone else encountered this issue or have any insights into these recent changes?

 

3 Replies

  • liamherbert1105's avatar
    liamherbert1105
    Copper Contributor
    I've had confirmation from Microsoft that those connector properties are no longer, and have never been, applicable to on-premise type connectors. So although the UI can't be used now, you only need to set affected properties to $false in PowerShell and then you may continue to edit them as required (only in PowerShell).
  • mitchw208's avatar
    mitchw208
    Copper Contributor
    Is there a remedy to this? Our public IP has changed recently and I have tried to edit our current SMTP relay connector. I am getting this error message.
    • Matt-Sywulak's avatar
      Matt-Sywulak
      Copper Contributor

      mitchw208 I have not found a remedy to this at all. Haven't had much luck with support just yet. It seems like if you're affected by the issue you're stuck between a rock and a hard place right now.

Resources