After enabling Mimecast for Inbound routing , Threat Protection Re-Writes the URLs for Safety. When this is enabled with the following 365 Spam Check : Image links to remote sites
Which : Messages that contain <Img> HTML tag links to remote sites (for example, using http) are marked as spam.
All Inbound emails with Images with Hyperlinks get marked as Spam by Office365. Make sure this is turned off!
https://docs.microsoft.com/en-us/microsoft-365/admin/misc/become-the-admin?view=o365-worldwide
Had to go through this process for a customer, because their VLSC account was setup at some stage in the past using [email protected] VLSC account as a work or school account, the domain was already registered against an unmanaged Azure AD directory, so we couldn’t set them up to use Teams. It’s a straight forward process just follow the article.
To find out if a domain is part of an unmanaged Azure AD directory, you can follow https://docs.microsoft.com/en-us/power-platform/admin/powerapps-gdpr-dsr-guide-systemlogs#determining-tenant-type as specified in the article.
The autodiscover process checks a few records , one of these is the root domain A record, and once you have an SSL certificate on your Web Server under cPanel, it intercepts the Autodiscover request cPanel believes it is hosting the email, and directs that to itself to its email servertrying to be helpful ( Instead of your Exchange server or 365 ) .
The email users are not setup on your cpanek, so no matter what you try, you will not be able to setup the user’s Outlook profile. This is the error I was getting in Outlook 2016. The error will be different for other versions of Outlook or if you are setting up the profile from Control Panel, but essentially it will not let you complete the profile setup.
The fix is quite simple, you just need to change the setting in cPanel or WHM (also owned by cPanel) from the default setting of “Local Mail Exchanger” to “Remote Mail Exchanger” and that’s it.
When trying to access another user Onedrive via the Admin portal of 365 , the new gui shows
“Loading Access Link” and no link is shown
The old Classic view you cannot click on the Access Files
This is due to the Administrator not have an Office 365 License , make sure one is assigned to get access to the App ( onedrive )
Recently a few users had the following bounce backs from Office 365 to an On-Prem Mailserver with the error
‘550 5.4.316 Message expired, connection refused(Socket error code 10061)
Checking the logs in 365 of this, this was due to the Fortigate adding some 365 SMTP servers to the IPS Quantarine List
Removing these servers from the Quarantine and also removing IPS checking in the Policy of 365 servers to on-prem via SMTP resolved this
Trying to setup a subdomain for iManage communication server in 365. I created a Connection from 365 to OnPrem server
Create a Connector
What I needed to do was also add the domain to 365 and change it to Internal Relay
Add the domain in below
Change the accepted Domain Type for the subdomain to internal relay
Azure Single Sign-On
Identifier (Entity ID): https://imanage.domain.com
Reply URL (Assertion Consumer Service URL): https://imanage.domain.com/api/v1/session/saml-login
Download Certificate file (.cer) and store on iManage server e.g. C:\SSL\
HIVE: HKLM\SOFTWARE\Interwoven\WorkSite\imDmsSvc
SAML Attribute: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name
SAML Endpoint: https://myapps.microsoft.com/signin/iManage%20SAML/xxxxxxx-xxxxxx-xxxx
SAML Key File: C:\SSL\iManageSAML.cer
SAML Logout Endpoint: https://login.microsoftonline.com/common/wsfederation?wa=wsignout1.0
SAML Web RP: https://imanage.domain.com
How to save existing Document library as Template
Login to Sharepoint then navigate to the Document Library
Go to Library Settings
Save template ( with or without the content )
Next go to the Site where you want to create the new Library and create a new App ( NOT Document library )
Search for your new Template
And Add this with the new Name
Recently had a user who when outside the office could not connect to 365. Per below her Outlook would just sit on “Trying to Connect”
They used OAuth for Outlook and 2fa which means when outside of a “trusted IP” the box should come up asking for the 2fa code , however this prompt was not coming up ever after restart (usually fixes a stuck Oauth box ) .
Fix
Go into credential manager and delete all the ADAL for the user , then restart Outlook
