So this is a follow up to the previous blog post here. Now for the vast majority of smaller business they'll primarily use Office 365 with very few services tagged on and this rule can be put into place with
Symptoms: CPU usage will spike to 100% and will be mostly used by the service "Azure AD Connect Health Sync Monitoring Service". Cause: .Net framework update before the software fully supports the underlying update. Workaround: stopping the service
Well today has certainly been interesting, teams as a possible slack killer! The lack of documentation to start with has been a bit disappointing. Enable in the portal The enabling is actually well covered on the blog article. To turn
Office 365 in general is a bit lax when it comes to default protection out of the box. I’ve found that a lot of malicious attachments come through in the form of js files, scr, zips, [insert next exploitable
Subscribe to TechFoundry
Subscribe today and get access to a private newsletter and new content every week!