SMTP Relay Connector working for one Tenant, Not working for a newly created Tenant

%3CLINGO-SUB%20id%3D%22lingo-sub-1943579%22%20slang%3D%22en-US%22%3ESMTP%20Relay%20Connector%20working%20for%20one%20Tenant%2C%20Not%20working%20for%20a%20newly%20created%20Tenant%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1943579%22%20slang%3D%22en-US%22%3EWe%20have%20had%20for%20years%20a%20supported%20Non%20TLS%20connector%2C%20filtered%20by%20fixed%20public%20IP%20Address%20on%20O365%20that%20we%20use%20to%20relay%20email%20for%20our%20printers%20and%20monitoring%20tools.%20This%20is%20set%20up%20on%20a%20tenant%20we%20have%20for%20years%20and%20It%20works%20flawlessly%20but%20due%20to%20having%20sold%20part%20of%20our%20business%20we%20need%20to%20change%20this%20configuration.%3CBR%20%2F%3EI%20thought%2C%20%22not%20a%20problem%2C%20let's%20get%20a%20new%20tenant%20on%20a%20different%20domain%2C%20set%20it%20up%20the%20same%20way%20and%20it%20will%20work%22.%3CBR%20%2F%3EWrong!%20Didn't%20work%2C%20supposedly%20because%20now%20Microsoft%20by%20default%20enables%20Security%20Defaults%20on%20new%20tenants%20(Annoying%20MFA%2C%20Etc)%2C%20sure%20you%20can%20disabled%20it%20but%20still%20doesn't%20work%20at%20least%20immediately%20and%20support%20seems%20to%20have%20checked%20everything%20I%20did%20and%20reached%20no%20brilliant%20solution....%20On%20why%20one%20Tenant%20works%20and%20other%20won't%20which%20is%20worrying!%20Just%20one%20idea%20of%20having%20something%20to%20do%20with%20tenant%20dehydration...%20They%20will%20call%20me%20today%20again%20to%20follow%20this%2C%20I'll%20update%20this%20thread%20afterwards.%3CBR%20%2F%3EIf%20someone%20has%20any%20thoughts%20they%20will%20be%20more%20then%20welcome.%3CBR%20%2F%3E%3CBR%20%2F%3E(%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fmail-flow-best-practices%2Ffix-issues-with-printers-scanners-and-lob-applications-that-send-email-using-off%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fmail-flow-best-practices%2Ffix-issues-with-printers-scanners-and-lob-applications-that-send-email-using-off%3C%2FA%3E%20)%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1943579%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor
We have had for years a supported Non TLS connector, filtered by fixed public IP Address on O365 that we use to relay email for our printers and monitoring tools. This is set up on a tenant we have for years and It works flawlessly but due to having sold part of our business we need to change this configuration.
I thought, "not a problem, let's get a new tenant on a different domain, set it up the same way and it will work".
Wrong! Didn't work, supposedly because now Microsoft by default enables Security Defaults on new tenants (Annoying MFA, Etc), sure you can disabled it but still doesn't work at least immediately and support seems to have checked everything I did and reached no brilliant solution.... On why one Tenant works and other won't which is worrying! Just one idea of having something to do with tenant dehydration... They will call me today again to follow this, I'll update this thread afterwards.
If someone has any thoughts they will be more then welcome.

( https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/fix-issues-with-printers-scanners... )
0 Replies