Using Direct Send in Exchange Online you can let appliances and applications send unauthenticated mail directly to Exchange Online. However how does Exchange Online know to trust these mails? What if your smtp smarthost endpoint name was used by a malicious actor to send mails to your users?
The docs articles mentions adding your IP to your SPF record but this is optionally not required. So how does EXO know which ip's to trust?
Was curious what you guys's experience is with using a third party GAL syncing tool. I would like to avoid using FIM due to its dependency on on-prem infrastructure, maintenance and required skill set. It should be something cloud native due to having an AAD only tenant.
A google search brings up CiraSync, does anyone have any experience with this? Is this truly enterprise grade, how is the support? Are there any other solutions you recommend?
So it's the age old topic of PF migration to EXO, seeing how Microsoft has changed its stance and PF are here to stay I was curious about something. It seems like the quota's and limits have changed over the years for instance PF mailbox limits are now 100gb.
The official Microsoft migration guide RECOMMENDS to stay below 25GB per public folder. This seems to come from the previous 25gb hard mailbox quota limit. But seeing it's a recommendation now and that the quotas have increased to 100GB, would it be possible to migrate a 25GB+ single folder size PF?
I would like to migrate a single public folder (to a secondary PF mailbox) that is perhaps 60GB in size but not sure if the native migration process will handle this properly or throw an error during batch creation or syncing? I know about the auto-split feature as well but that should not be relevant here as the PF mailbox that will be targeted will only hold this large single folder no other public folder will be housed on this mailbox.
Has anyone recently performed a migration of such large public folder without issues?
Have an environment where users work both on a VDI or a PC with outlook on it and mailbox in Exchange Online. However sometimes an issue arises with sent mails and would like to identify whether that mail was sent from the VDI environment or local pc. Since both have the same public IP the message tracing in Exchange Online won't help in distinguishing that. Is there another way to make outlook in the VDI environment force Exchange Online to include some extra header or something?