Tenant to Tenant Mail send as permission

%3CLINGO-SUB%20id%3D%22lingo-sub-344327%22%20slang%3D%22en-US%22%3ETenant%20to%20Tenant%20Mail%20send%20as%20permission%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-344327%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20engaging%20a%20third%20party%20company%20who%20will%20be%20processing%20email%20requests%20on%20our%20behalf.%20The%20idea%20was%20to%20have%20a%20forwarder%20set%20to%20forward%20the%20support%20calls%20onto%20the%20third%20party%20and%20then%20add%20their%20mail%20server%20to%20our%20SPF%20record%20to%20allow%20them%20to%20send%20as%20our%20domain.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20turns%20out%20%2C%20the%20third%20party%20company%20are%20also%20on%20Office%20365%2Cso%20I%20assume%20we%20won't%20need%20to%20add%20anything%20to%20our%20SPF.%20As%20both%20sides%20are%20on%20Office%20365%20%2CI%20have%20a%20few%20questions%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20How%20can%20we%20authorise%20the%20other%20tenant%20to%20send%20on%20our%20behalf%20if%20both%20sides%20mail%20server%20is%20Office365%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2.%20Am%20I%20missing%20any%20features%20within%20Office%20365%2FExchange%20online%20that%20makes%20this%20scenario%20easier%20to%20implement%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMany%20Thanks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-344327%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-386291%22%20slang%3D%22en-US%22%3ERe%3A%20Tenant%20to%20Tenant%20Mail%20send%20as%20permission%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-386291%22%20slang%3D%22en-US%22%3E%3CP%3E1)%20You%20can%20only%20connect%20a%20single%20e-mail%20domain%20to%20a%20single%20Office%20365%20tenant%3B%20a%20tertiary%20(sub)domain%20is%20perhaps%20more%20ideal%2C%20for%20sake%20of%20routing%20bulkmail%20and%20seperating%20mail%20flow.%3CBR%20%2F%3E2)%20That%20said%2C%20bulkmail%20is%20limited%20in%20365%20(there%20are%20limits%20in%20message%20sending%2Fno.%20of%20recipients%2Fetc).%20So%2C%20usability%20for%20your%20scenario%20depends%20on%20volume.%20If%20not%2C%20you%20(they)%20may%20need%20to%20look%20at%203rd%20parties.%3C%2FP%3E%0A%3CP%3EMore%20info%20in%20EOP%20limitations%2C%20see%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fservicedescriptions%2Fexchange-online-protection-service-description%2Fexchange-online-protection-limits%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fservicedescriptions%2Fexchange-online-protection-service-description%2Fexchange-online-protection-limits%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

Hi All,

 

We are engaging a third party company who will be processing email requests on our behalf. The idea was to have a forwarder set to forward the support calls onto the third party and then add their mail server to our SPF record to allow them to send as our domain. 

 

It turns out , the third party company are also on Office 365,so I assume we won't need to add anything to our SPF. As both sides are on Office 365 ,I have a few questions:

 

1. How can we authorise the other tenant to send on our behalf if both sides mail server is Office365?

 

2. Am I missing any features within Office 365/Exchange online that makes this scenario easier to implement?

 

Many Thanks

 

1 Reply
Highlighted

1) You can only connect a single e-mail domain to a single Office 365 tenant; a tertiary (sub)domain is perhaps more ideal, for sake of routing bulkmail and seperating mail flow.
2) That said, bulkmail is limited in 365 (there are limits in message sending/no. of recipients/etc). So, usability for your scenario depends on volume. If not, you (they) may need to look at 3rd parties.

More info in EOP limitations, see https://docs.microsoft.com/en-us/office365/servicedescriptions/exchange-online-protection-service-de...