When you create an
Intune tenant within your environment, you execute the creation with an account
which is Global Administrator within Azure Active Directory. And in my work as
an indendent consultant I see a lot of companies which keep using the account
with Global Administator rights to manage their Microsoft Intune environment as
While for initially
setting up some Azure AD functionality Global Administrator rights might be
needed, this is only the case during the setup phase. Once you have implemented
your environment, you hardly ever need the Global Administrator rights and for
most tasks they are not needed perse. Think of the Global Administrator rights
as an equivalalent of the Forest Administrator/Schema Administrator group
within Active Directory.
Disclaimer: This post is written on December 4th 2019 and reflects the state of this functionality at that point in time.
When you host your email on the Exchange Online (EXO) platform part
of Office365 you can implement several security measures to make sure that
email send from your domain gets delivered to the mailbox of the recipient.
The most known solution for this is by implementing a Sender Policy
Framework (SPF) DNS record. By creating a SPF DNS record in your DNS you
provide receiving email servers the option to check if the originating IP of
the email is also the authorized email server for the domain. If not the email
can be considered suspicious and the email system from that point forward can
decide to threat the email as spam, phishing and so forth.
If you decide to make the nameservers of Microsoft authoritative,
which allows you to manage your DNS settings from the Office administration
portal, the SPF record needed can automatically be enabled for you.
One of the
disadvantages of being an experienced consultant in IT is the fact that once in
a while you need to re-learn. With re-learn I mean that for some concepts it’s
easier to understand how it works if you come from no-experience. I’ve
experienced this with quite some Microsoft products as well. If you know the
old version, switching to concepts in a new version might not be that easy
compared to when you get to know the new version without any prior knowledge.
I also experienced
this “challenge” lately when trying to figure out when to assign
applications or configuration to either User Groups or Device Groups.
While browsing the
new Microsoft 365 Device Management portal I noticed the following option:
“Guided scenarios (preview)”. From the What’s
new in Intune page it seems that this functionality was released in the
release of October 14th 2019.
Disclaimer: This post is written on Oktober 29th 2019 and reflects the state of this functionality at this point in time.
So, what’s a guided
scenario, you might ask, Microsoft explains it as following: “A guided scenario is an end-to-end experience in
Intune where you can tackle a big task, in a single workflow. Assemble
policies, apps, assignments, and other management objects into a reusable
collection that you can deploy as many times as you want.”
Technically, Guided scenario’s provide a way to create a policy set based on a scenario, something I already blogged about here: “So what are policy sets?“
Intune at my customers I rarely encounter green field implementations where
computers and mobile devices are newly delivered and no data needs to be
restored on the device. Most of the time, the devices are already in use and we
need to figure out some strategy to deal with the data from the device, before
we re-install the device and bring it under management.
For iOS devices I
recently did some testing about the possiblities of restoring iTunes backup to
devices which are re-enrolled into Intune, therefore receiving a Management
Starting with the Intune
release from October 14th 2019, Microsoft made available a new
functionality called “Policy Sets”.
Even though there a now (at time of writing this article) still in
preview, they are a very welcome addition to the Intune options available.
In my blog article series on Conditional Access Demystied I mentioned that Conditional Access can be used to route sessions toward Microsoft Cloud App Security (MCAS). In this article I will go into more detail on what MCAS is, and how to setup Conditional Access App Control.
Disclaimer: This article discusses the full option MCAS product, there are some other flavors providing partial functionality like Office 365 Cloud App Security and Cloud App Discovery (CAD). For information about licensing, see the Microsoft Cloud App Security licensing datasheet.
TL;DR; – When reinstalling Windows on a Surface Pro 6 and it fails, make sure that you “temporarely” disable the ” Enable boot configuration lock” option and try again.
At one of my
customers we are using MDT to install Surface Pro 6 devices in order to make
sure that the latest version of Windows 10 is available when starting the Out
of the Box Experience (OOBE).
While testing this solution, we experienced some machines starting to fail to install Windows 10, where MDT would exit with the following error code: Litetouch deployment failed, Return Code = -2147467259 0x80004005
In Q1 2017 Microsoft
released the Pass Through Authentication (PTA) functionality as part of Azure
AD connect. With the release of Azure Active Directory (Azure AD) Pass-through
Authentication allowed for your users to sign in to both on-premises and cloud-based
applications using the same passwords without the need to implement a Active
Directory Federation Services (ADFS) environment.
With this options we
now have the following authentication options available when setting up a hyrid
Privacy & Cookies Policy
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.