To block users from creating trial and adhoc subscriptions for Office 365 services or even PowerPlatform services you can turn a switch and block it.
Set-MsolCompanySettings -AllowAdhocSubscriptions $falseTo check if this is set to “False” for your tenant you can run this
Get-MsolCompanyInformation |fl AllowAdhocSubscriptions 
The first step into enabling the use of Unified labels in Office Web apps is here! Today i got the “Sensitivity” bar enabled in my tenants.
Sorry for the Norwegian text in the picture, as “Følsomhet” is the Norwegian word for “Sensitivity”
To get started with Sensitivity labels – head over to Microsoft 365 Security portal and open the “classification” menu.
From there head in to “Sensitivity” and create a label.
Next – choose the tab for Label Policies and publish the label you created.
When testing the feature, remember to only publish the label to your self so that you not enable all users in your company to use and test it. 🙂
So if you are using Office 365 you should consider use/enable these 5 features which you have free of charge within your Office 365 subscription.
These tips are the first thing i enable for my customers (if they are not enabled already of course)
So let`s dig into the features! – All of the features are FREE!
1. Enable MFA for your user
This is a simple thing to do and in 5 steps it`s enabled both for your end-users and for your admin accounts.
2. Block malicious files types
The next one is almost as simple as the first one and is enabled in just a few minutes.
Navigate to “protection.office.com” and authenticate, go to “Threat Management” and “Policy” then click “Anti-malware”. Edit the default policy and og to settings, under “Common Attachment Types Filter” set the toggle to “On” – your done! 🙂
3. Use a separate account for administrative tasks
A simple thing to do – if you have administrative privilege’s on your account you should create a separate admin account which is protected with MFA of course. This can also be mitigated using the paid service Azure AD Privileged Identity Management – more on that service i a later blogpost
4. Block Auto-forwarding on email accounts
By blocking auto-forwarding on email accounts you mitigate the attack vector which is when a account is breached and the bad guys setting up forwarding of emails to gain information about the company and how people collaborates. This is the start of a advanced phishing attack.
5. Use Secure score to improve security
Secure Score is a simple and fun way to fix and improve your company security. The results are tailored to your Office 365 implementation and you`ll get scored on how many improvements you configure.
So to wrap up this blog post – All these features are free! It will take you under 1 hour to implement and your company is a lot more secure!
The Automated Investigation & Response feature under Threat management in Security & Compliance admin portal is a pritty new and amazing feature in Office 365.
To use this feature you need to have “Office 365 Advanced Threat Protection Plan 2” licenses witch you can purchase standalone or it`s included in the Office 365 E5 license and yes – you need to be a “Global Administrator” or “Security Administrator” to configure the service. Once configured you can also use “Security Reader” or “Security Operator” to see whats happening.
Have a look here to see all capabilities within “Advanced threat protections”.
So over to Automated Investigation & Response (AIR) – have a look at this screenshot
As we see her we have two detection on-going which waiting on user action. The first one in the picture is automatically found by the system and the second one is a email which I reported through the “Message Report” add-in for Outlook which are deployed to all users (Both Outlook and Outlook Web).
In the overview of the case (the one i reported) we see what`s going on with the message, the Trigger alert, what threats who where found, how many emails are “infected” and which users that have the infected email in their mailbox (could be a mass-phishing attack)
When we navigate to the Email tab we see what section of the email that are found malicious and in this case the Advanced Threat Protection has matched the URL to a malicious URL
Moving to the Action tab – we are given several a big tool belt meaning that we can do a soft delete from the users mailboxes (in this case only one user, but if this malicious email was delivered to 100 users we can in one click remove the email from the users mailboxes) and block the URL in Safe Links.
So this was very short on how to easily use AIR in your tenant if you have the right license.
So in the previously post I went through how to activate MFA for Administrator roles i a really simple and effective way.
In this post we will focus on activating MFA for all regular users. And first off all we need to evaluate who should be activated first or should we activate on all users at the same time and do a evaluation on service accounts! If we enable MFA on for example a serivce account used for scan to email on “multi functional printers” or on a mailbox account witch are used on a thirdparty ticketingsystem (POP/IMAP) we could break those service by just enabling MFA on all users.
My recomandation is when you are more then 30 users in your company you should select a few ambasadeurs who is getting the MFA activated first and can therefore be the power users who can help others with the registration if there is any hick-ups (should not be many).
And to activate MFA for end users I highly recomend to use Conditional Access for
Easy like that! And It`s a realy quick solution for your company.
Drawback here is that you need “Azure AD Premium P1” licenses to use Conditional Access and a second drawback is that it`s not scored at the Microsoft Secure Score.
You problably heard about multifactor authentication by now, but have you enabled it in your environment?
If not! Please do so at once! I will in this short blogpost give you the direction to get started with MFA in Azure AD.
So let`s just jump right into it.
First things first – protect your admin accounts!
With admin accounts i mean a account who has a additional role assigned other then beeing a regular user and to mitigate these users we will enable a Conditional Access who is requires MFA for all administrator accounts
So navigate to Azure Active Directory in portal.azure.com
Dive into “Security” -> “Conditional Access”
Click the “Baseline policy: Require MFA for Admins (Preview) and choose to use it immidiatly
So now you have successfully enabled MFA for all your admins! Great work 😊
To make it easier for yourself you can now change the MFA verification from the default SMS to Authenticator app by visiting https://aka.ms/mfasetup and add the Authenticator app as a preffered method.
Next up is to enable it for all your users and that i will cover in the next blog post – Stay tuned for “Get started with MFA – Part two” 🙂
Når vi snakker om skyen er «Device management» for mange et “glemt” kapittel, i alle fall for små og mellomstore bedrifter i Norge. Device management i skyen ble tidligere omtalt som MDM (Mobile device management), og mange tenkte nok at det bare gjaldt for Mobiler og nettbrett, – men tiden har endret seg og MDM omfavner nå PC og Mac`er også!
Microsoft sin Intune-løsning har støtte for både Windows, MacOS, Android og iOS pr. dags dato. Dette betyr at de støtter de største operativsystemene som brukes ute i norske bedrifter.
Men hvorfor trenger akkurat du dette? Er det ikke greit at de ansatte selv har kontroll på maskinene? Jo, kanskje, men hvordan håndterer vi da bedriftens data som lagres på de ansattes telefoner eller pc`er?
Med Office 365 er bedriftens data veldig enkel å få tilgang på, det holder at man logger seg inn på “office.com” med brukernavn og passord (+ MFA selvsagt) så har man derfra tilgang til epost, felles dokumenter i SharePoint, hjemmekatalogen i OneDrive for business eller andre sky-tjenester som er tilgjengeliggjort igjennom portalen.
Ok, så hva skal Intune hjelpe til med?
Overordnet i en cloud only konfigurasjon vil det se slikt ut:
Ved at brukernes enheter registreres i firmaportalen (Intune-app) eller i Azure AD så vil man få kontroll på hvilke enheter brukerne har og får tilgang til bedriftens data med.
Man kan lage samsvars krav til enhetene, som for eks. krever at maskinen har Antivirus, er oppdatert med siste oppdateringer og har kryptering av harddisken, før den blir markert som en “godkjent enhet”. For Windows 10-maskiner kan man konfigurere opp til 28 sjekker, for MacOS opp til 18 sjekker. Man kan virkelig sette krav til enheten man skal dele alle bedriftshemmelighetene med.
– Ved bruk av Conditional Access sammen med Intune kan man kreve at enheten skal være “Compliant» i henhold til samsvarskravene vi konfigurerte i punktet over, om man skal kunne logge på “Office.com” og starte SharePoint.
Når man nå har registrert de mobile enhetene, som brukerne også bruker for personlige filer, får man et skille på bedriftsdata og personlige data i applikasjonen. Dette betyr at dersom enhetene blir stjålet, eller at den ansatte slutter i firmaet, kan man ved et par klikk slette bedriftens data (dokumenter, epost osv.)
Man vil kunne blokkere datakopiering mellom den private delen av applikasjonen og den bedrifts-eide delen.
So in the recent time i have been working with a customer to integrate Exchange Online mailboxes into a customer support application witch are using POP. The application throwed a error message:
02:47:34.513 Trc 21628 [MsgIn-2] <pop-client1> Mailbox account 'yourmailbox@domain.no'[https://outlook.office365.com/EWS/Exchange.asmx:443]: opening mail folder 'INBOX'
02:47:34.748 Std 21627 [MsgIn-2] <pop-client1> No INBOX Folder found on Corporate Email Server
This indicates that the software witch is polling emails need the inbox folder to be “Inbox” and not “innboks” (witch is Inbox in norwegian). So we need to change the default folders to match the language set in OWA.
3. Select General in the left pane and then click on: Region and timezone.
4. In language, set your language for OWA and check the checkbox witch also renames the default folders to match the selected language and hit the save button.
When activating Known Folder Sync in OD4B the sync never starts due to folders that cannot be synced.
These folders are Junction folders on the drive and needs to be deleted.
First do a dir in the users document folder and look for hidden files like this:
C:\Users\USER\Documents>dir /ah
Volume in drive C is Windows
Volume Serial Number is 903B-D31E
Directory of C:\Users\USER\Documents
18.04.2018 10.10 2 230 Default.rdp
26.09.2018 11.59 402 desktop.ini
26.09.2018 11.59 Intern video [C:\Users\USER\Videos]
26.09.2018 11.59 Min musikk [C:\Users\USER\Music]
26.09.2018 11.59 Mine bilder [C:\Users\USER\Pictures]
2 File(s) 2 632 bytes
3 Dir(s) 55 879 593 984 bytes free
Then delete the junctions like this:
C:\Users\ÙSER\Documents>rmdir “Intern video”
C:\Users\ÙSER\Documents>rmdir “Min musikk”
C:\Users\ÙSER\Documents>rmdir “Mine bilder”
Other files in conflict with the sync needs to be removed from the local machine before the cloud sync can start. Backup and move the files in case of future needs.
Happy OneDriving.
© 2020 IdefixWiki
Theme by Anders Norén — Up ↑