So these day`s we all uses MFA right? But not all MFA methods are as good as we think.
There have been several cases where “SIM Swapping” or “SIM Hijacking” has been the case and therefor – can we trust using SMS for Multi-Factor Authentication?
In short notes this is how SIM Swapping is done.
You loose personal information.
Your information is used to gain trust at the mobile carrier to convice them to switch from current to new SIM card (the new SIM is already in the hands of the bad guy)
With controll of mobile number the bad guy log`s onto your services with one-time password or completing MFA challenge.
Your account is compromised
With that said, you should disable SMS as an authentication method. See my other blog post on how that`s done!
Since you now uses Microsoft Authenticator as your primary MFA factor you get a push notification with “Allow” or “Block” access whenever the authentication is done. At this point the bad guy start using a method called “MFA Fatigue attacks” and blasts lot`s of authentications against you, and somethimes a user clicks on “Allow” and thinks; “It`s most likely my phone or tablet or something…”.
But with the new capabilities from Microsoft within using Azure MFA you can now add “Number matching” and “additional context” to the signin (both features are in preview at the momemt (04.05.2022).
OK – so here`s how it looks!
So you see that when ever the authentication is done a number is shown and it needs to be matched on your Microsoft Authenticatior application. In addition we also see a map and location of where the authentication is getting from!
Here`s how you can configure it!
Head over to portal.azure.com
Navigate to Azure AD -> Security -> Authentication methods and click on “Microsoft Authenticator”
Hit “Add users and Groups” and add a group or user to test with and click “Select”
Then open the settings of the group and “Require number matching” and “Show additional context in notifications”
There you have it! Next time you authenticate with a user that`s configured to this setting you will get a number matching 🙂
Ever thought about your end-users really think before clicking?
How often does your end users (who have local administrator rights in some way) just install stuff without thinking?
To start with, your end-users should not be local administrators on their machines, but many still are. If they are not all the time lot`s of companies have sollutions where end-users can elevate them self for a certain time frame.
But let`s make them think an extra time before actually installing stuff that require administrator privilegdes on their machine by forcing them to type their username and password instead of just “Yes/No”.
One way to change this is to use the Registry and force the UAC to prompt username / password.
Ever stubled over the need of changing a guest`s sign-in information on one or more guest accounts? Well, this has been a issue for several companies and the way forward was to delete the guest accounts and re-invite them.
When doing this all access to Teams, SharePoint Online and OneDrive for business for that guest account was also deleted and they needed to be added to the resources again with the new guest account.
A new configuration within Azure AD now gives you the ability to change the E-mail address for the user and reset the sign-in information – and it`s quite easy!!
Let`s go through the config changes and change a guest account`s sign-in information.
So! I have 1 guest account “firstname.lastname@example.org” and this guest account have access to 1 Team.
I want to change the sign-in information for this user (at the same time as the PTaken.no company changes the UPN on their side.
So let`s change it at our side,
We edit the guest account and set the new UPN on the user on the “email” and “alternate email” attribute like this – (the old UPN was email@example.com).
When this is changed we can go ahead and re-send the guest invitation to the new address by clicking the “Invitation Accepted” button and reset invitation status.
The guest now get`s a new invitation that needs to be accepted
Now when the guest is signed into for example Microsoft Teams the account will show that he is logged in with the new UPN.
After two years of “blog silence” from me, i`m no working on several new blog posts and are accelerating my community work again!
2020 and 2021 was two years where the work presure was very very high and automaticaly community work was not prioritized due to high prio on family life on all ours available after delivering my working hours.
anyhow! All that behind – and 2022 will be “The year of community” for me!
With several blog post ready, the planning of several in-person “Office 365 User Group Agder” meet-ups and also several call-for-paper delivered to conferences and communities!
Windows365 is a Cloud pc for all users and it`s so easy to start using! In this post I will go through a setup of Windows365 Business in a cloud only tenant and show you how fantasticly easy this is!
There are some pre-requisites that need to be taken in considiration and I`l list them here
Azure AD – IAM
Maximum 300 users in your tenant
Microsoft Endpoint Manager (Intune) for admin/config
So with that “short” list the joker here is that you should have Intune configured allaready as that makes the Windows365 deployment soooo super easy.
Let`s first talk about licenses.
There are Windows365 Business and there is Windows365 Enterprise, as mentioned I will cover the Business version here – so let`s have a look at the different machine sizes.
The pricing is ranged between $24 for the cheapes one and $162 for the most expensive one with most vCPU`s, most RAM and biggest Storage.
1 vCPU and 2GB RAM + 64 GB Storage
2 vCPU and 4GB/8GB RAM + 64GB/128GB/256GB Storage
4 vCPU and 16GB RAM + 128GB/256GB/512GB Storage
8 vCPU and 32GB RAM + 128GB/256GB/512GB Storage
So there are some different licenses to choose from as you see. 12 of them to be exact and i`m guessing everyone can find a license fitting their needs.
In my scenario I`m using the $45 machine with the spec`s “2 vCPU, 8GB RAM and 128GB Storage” this is a machine that run`s the most of my regular work tools.
Provisioning the beauty!
So to the easy part! First off is to buy the license that you need based on your machine size – and when that`s done just simply add the licence to the user you are going to provition a cloud PC for.
The user (maybe your own..) can simply logon to https://windows365.microsoft.com/ and access the machine 🙂 First time when you click the to connect the machine it will provition and get ready – in my case this took about 30 minutes – but after that the machine was ready for me to connect to.
about 1 hour later the machine was reporting into Intune that it`s a Compliant computer just like any other physical machine out there!
From the management pane of your cloud pc you can do actions like Restart, Reset, Rename and Troubleshoot.
De-provisioning and cleanup
This is even easier! Just remove the license from the user and the Cloud PC is removed after approximently 30 minutes.
So! I`m back again after not blogging, speaking or “anything” for the community for the last one and half year (since the pandemic started in Norway 12.03.2020)!
I have been spending the summer in paternity leave at home with my 1 year old son and been been recharging my batteries to full and from now on I will be starting with community work again as I feel ready to meet, great and have fun with all you fellow community people again.
The pandemic has physically drawn me down to a place where i have not been able to contribute to the community at all. I used all my energy on delivering my hours at work and spending time with my family at home.
Now that we see the end of the pandemic i feel energized and ready to work hard both from our company offices and from home when that`s needed!
Next community talk is our “Office 365 User Group Agder” meetup in Kristiansand Norway where I will be delivering the “What`s new” section. This will be a in-person event with both food and drinks complimented to our guests! SO EXITED!!
I will also work hard on getting back on stage on other conferences and meetups moving forward!
The new built-in admin consent workflow within AzureAD Enterprise Application is amazing!
This feature will give you the control that you need to take care of your companies sensitive information like user id`s, files, email accounts etc.
Did you know that malicious applications is often a start of a sophisticated phising attack?
If a malicious application get`s the right permissions it could be a bad situation for your company!
Just have a look at this random application and what that app can retreive, other also gives a complete user list of all the employees back to the app developers.
In this case ALL files that this user has access to does this app now have access to read – meaning that`s there is no secrets anymore..
So to be able to block and and have controll over the applications that get`s granted to your AzureAD tenant you should use the new “Admin Consent Workflow” within AzureAD. This feature is in preview at the moment but I highly recomend using it.
It takes two minute to configure and after it`s configured the users see`s this when trying to connect a thirdparty application to your tenant
After this request is sent – the admin that is configured within the workflow get`s an approval email and can easlly approve consents 🙂
The configuration looks like this:
Please have a look at the official documentation and enable it for your deployment!
If your Microsoft 365 tenant like mine is located in a region that not`s include your country then this is how you should configure your tenant to get the data as close to you as posible!
(if Microsoft has opened a Datacenter in your country of course :))
Why move your data?
There are several improvements by getting your data moved to a closer datacenter.
Improved latency to the services
Data stored in your own country
Still have DR capabilities outside of your country if infrastructure failes
Multi-geo capabilities to many more closeby countries for your staff
The latency improvements are incredible! I have noticed this when using a SharePoint Online site located in Europe vs. In my home country Norway. The latency against Norway was much much better and when using the service it feels much more “snappy”.
Creating a new Microsoft 365 tenant for everyone living in Norway will create the data store in Norway aswel for the services
When to do it?
Microsoft has released a table of when the Request period for requesting a move of data, take a look here to have a look for your country!
For us in Norway this means that we need to opt-in by the end of October to be migrated and get our core customer data at rest in Norway.
When will your data be moved?
A catch with all this is that Microsoft says that they may use 24 months to move your data! TWO years for migrating it to new datacenters.. But that said, it can happend faster. After you request a move of data, Microsoft will plan to move your company data as soon as operational constraints allow.
How to request a move of data?
It`s quite easy to request a move of data!
Head in to “Settings -> Organization profile -> Data residency” and check the checkmark and “Save changes” then wait 🙂
To look at where your data is at the moment head into the “Data location” in the same menu under Organization profile and have a look 🙂
In this post I want to go through some steps that I think is quickest method to get started with Microsoft Endpoint Manager. This will not cover ALL the features but it will give you an quickstart to the service.
For instance, what shold you start with?
To be honest, start with something easy and creates quick ROI (Return of investment) and that could be more than just how to get my money back – rather it could mean that your infrastructure is getting more secure.
So to start with something “easy” let`s kick it of with mobile devices. Many companies does not have any Mobile device management in place and their Cloud services is available for EVERYONE to attache to. So let`s start with demanding compliant devices and closing the door for others!
Requirements: Microsoft 365 E3 / E5 or EMS E3 / E5 or Intune licenses
Devices Android devices will work straight “out of the box” with Intune but to be able to join iOS/iPadOS Devices to Intune we need to generate and apply a “Apple MDM Push certificate”.
Let`s start with the Certificate for Apple devices (this certificate is also needed for MacOS devices). The only thing you need here is an Apple ID and follow the guide from “Devices -> iOS enrollment -> Apple MDM Push Certificate”. When this is in plnace we can procede.
When it`s created you have a valid Certificate for the next 365 days. That means that you need to remind your self to renew the certificate every year! When the certificate expires your intune services will stop against Apple devices.
So what is a compliant device?
A compliant device is a device registred to Intune and has passed the Compliance policy that you have created.
The policy can contain several “settings” that must be enabled or set on your device for it to be marked as “Compliant Device”. For iOS/iPadOS we have at the moment (04.04.2020) 17 settings we can check to validate the device and for Android 19 settings (04.04.2020).
Here is a simple set of compliant device policies for Android and iOS.
Navigate to “Devices -> iOS -> Compliance policies” and create a new policy. Give it a name, set some settings and click create. In this policy i have just put on two settings, “block Jailbroken devices” and “Require password to unlock device”
Hit Create and go to “Assignments”, in this menu we will assign the policy to all users so that everyone that tries to enroll their device will get the policy. (this is the same step for both iOS and Android).
Navigate to “Devices -> Android -> Compliance policies” and create a new policy. Give it a name, set some settings and click create. In this policy i have just put on two settings, “block Rooted devices” and “Require password to unlock device”
And like the iOS policy we need to assign it to all users, so head in to Assignents after creating the policy and assign it to all users.
Block devices that are not compliant
To block users from connecting with other devices we will use Conditional Access to prevent devices that are not enrolled in your organization. The policy is created from the Microsoft Endpoint Manager portal under “Endpoint security -> Conditional Access. Create a new policy and name it “Require compliant devices”
The policy looks like this and will of course not block the Intune enrollment portal 😊
Users and groups
Include all users and create exclution for users you want to exclude from the policy
Cloud Apps or actions
Include “All cloud apps” and click on “Exclude” and search after “Microsoft Intune Enrollment”
Device platforms, configure it and choose Android and iOS from the list.
Grant access and choose “Require device to be marked as compliant”
Now you can enroll your first device, i`ll show it with an iPad her, but first you need to downlod the Company Portal to your iPad.
Then you stat the application and sign in – then starts the enrollment of the device.
When that`s completed the device is registred in the Device pane in Microsoft Endpoint Manager Admin Center and you`ll see complance status on it.
That`s it! Now you have a new requirement for all users, they need to enroll their devices (mobile devices) within Microsoft Endpoint Manager to gain access to cloud resources!