This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 64%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDR%3C/text%3E%3C/svg%3E)
Not able to whitelist a subnet x.x.x.0/23 in O365 connector. I have set up a connector to allow devices to send email using O365 but somehow the connector only allows /24 - /32. Is it possible to work around this.
Not possible by design.
Use a transport rule instead:
https://learn.microsoft.com/en-us/microsoft-365/security/office-365-security/configure-the-connection-filter-policy?view=o365-worldwide#skip-spam-filtering-for-a-cidr-ip-outside-of-the-available-range
AndyDavid.
Thanks for your response. I have added the IP range to Bypass the Spam Filter but on the device they are still getting the error that connection to the email server failed. I added the individual printer IP addresses to the mail relay on Exchange on prem and they are able to send email but it fails when I use O365. The host name I am using is the O365 MX record domainxx-com01e.mail.protection.outlook.com
Did you create a transport rule? IF so, what does it look like?
According to the recommended Microsoft doc, I created a rule to bypass spam filter and added sender IP addresses (xx.xx.xx.0/23), set the SCL to Bypass spam filtering and mode of the rule is enforced.
Are the messages being picked up by any rules above it?
Look through message tracking to see if that is the case.
You shouldnt see a connection error if the messages are being accepted by the Exchange Server so ensure your receive connectors are configured to accept these messages as well
No messages are being picked by other rules. I have looked through message tracking and that's not the case. I am working with my network team to see why this is happening. I have reverted back using our Exchange on-prem mail relay for now which is working until I figure out what the issue is.
Thanks alot AndyDavid
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 82%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEY%3C/text%3E%3C/svg%3E)
Hi,
I am writing here to confirm with you how the thing going now?
If you need further help, please provide more detailed information, so that we can give more appropriate suggestions.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi Eric,
I do not need further help. I appreciate the info Andy provided but I decided to point the device to our on prem mail relay instead for now until I figure out the issue.
Thanks