CHI-LTD
asked on
Synchronising Azure (o365) with mimecast
We are trying to get the above working and MS cannot help at all, whereas and mimecast believe the tenant account is wrong as per https://community.mimecast.com/docs/DOC-1011
i have configured the tenant account domain.onmicrosoft.com but it still fails.
Anyone else using this?
Thanks
i have configured the tenant account domain.onmicrosoft.com but it still fails.
Anyone else using this?
Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
also if you can, provide a screen shot of the configure tab so i have a look.
ASKER
Correct, we cannot get Mimecast to sync with azure.
Azure-Application-Settings.jpg
Azure-Application.jpg
Azure-Application-Settings.jpg
Azure-Application.jpg
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
its now showing as working...
how odd. ill speak with mimecast.
how odd. ill speak with mimecast.
glad you fix that up :)
ASKER
But not showing the journaling.journal.domain. com account that the mimecast service needs to journal these emails.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So within Mimecast: directories - internal - we have on prem production domain and an o365 domain.
Mimecast archives emails as they pass through their service and archive within their own mailboxes which are synchronised by our dirsync software.
Yes ive followed this article
Mimecast archives emails as they pass through their service and archive within their own mailboxes which are synchronised by our dirsync software.
Yes ive followed this article
ASKER
Here is what i see for our production domain
mimecast-archiving.jpg
mimecast-archiving.jpg
i think you have asked another question after Mimecast have been successfully sync with Azure AD.
you should not see any of the @journal.domain.com as they are created in mimecast portal only. There are no present in Azure AD. you should not require to create it in Azure AD anyway.
you should not see any of the @journal.domain.com as they are created in mimecast portal only. There are no present in Azure AD. you should not require to create it in Azure AD anyway.
ASKER
was mimecast issue in cloud