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?
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• RestrictDomainsToIpAddressesThis 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? Read More
