SOLVED
Home

Default security settings for Office 365 for first account logon on new device

%3CLINGO-SUB%20id%3D%22lingo-sub-188218%22%20slang%3D%22en-US%22%3EDefault%20security%20settings%20for%20Office%20365%20for%20first%20account%20logon%20on%20new%20device%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-188218%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20trying%20to%20figure%20out%20where%20to%20change%20the%20security%20settings%20on%20Office%20365%20when%20a%20user%20logs%20on%20to%20a%20new%20device%20for%20the%20first%20time.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStory%3A%20I%20created%20a%20new%20Office%20365%20tenant%2C%20added%20some%20standard%20users%20(no%20sync%2C%20just%20cloud%20users)%2C%20leaving%20all%20settings%20at%20their%20defaults.%20This%20means%20no%20MFA%2C%20no%20extra%20device%20policy%2C%20etc.%20Then%20I%20joined%20a%20new%20%2F%20re-installed%20Windows%2010%20laptop%20to%20Azure%20AD%20by%20selecting%20'this%20laptop%20is%20for%20work'%20in%20the%20OOBE%20(aka%20first%20run%20experience).%20Then%2C%20again%20using%20a%20standard%20user%2C%20I%20get%20two%20remarks%20regarding%20authentication%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3EA%20PIN%20code%20is%20required%20for%20extra%20security%20at%20logon%26nbsp%3B(%22Your%20organization%20requires%20Windows%20Hello%22)%20%26gt%3B%20Set%20up%20PIN.%3C%2FLI%3E%3CLI%3EThe%20user%20needs%20to%20confirm%20its%20identity.%20(%22Your%20admin%20has%20required%20that%20you%20set%20up%20this%20account%20for%20additional%20security%26nbsp%3Bverification%22)%20%26gt%3B%20Set%20it%20up%20now.%20Options%20are%20phone%20call%2C%20SMS%20or%20mobile%20app).%3C%2FLI%3E%3C%2FOL%3E%3CP%3EDuring%20testing%2C%20it%20seems%20that%20step%202%20is%20a%20consequence%20of%20step%201.%20But%20I%20am%20not%20100%25%20sure.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20question%20is%3A%20where%20do%26nbsp%3Bthese%20requirements%20come%20from%3F%20I%20haven't%20set%20any%20of%20these%20settings.%20I%20looked%20'everywhere'%20in%20the%20Office%20365%20admin%20portal%20and%20in%20the%20Azure%20Portal%20but%20could%20not%20find%20any%20setting%20that%20regulates%20this%20experience.%20For%20example%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EAAD%20admin%20center%20%26gt%3B%20Devices%20%26gt%3B%20Device%20Settings%20%26gt%3B%20Require%20MFA%20to%20join%20devices%3A%20No%20(%3Ddefault)%3C%2FLI%3E%3CLI%3E%3CSPAN%3EAAD%20admin%20center%20%26gt%3B%20Devices%26nbsp%3BPassword%20Reset%20%26gt%3B%20Registration%20%26gt%3B%20Require%20users%20to%20register%20when%20signing%20in%3A%20No%20(switched%20from%20the%20default%20yes%2C%20but%20as%20expected%20had%20no%20effect)%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CSPAN%3EI%20tested%20this%20on%20two%20new%20tenants%2C%20with%20two%20laptops%2C%20and%20the%20experience%20was%20the%20same.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20want%20to%20disable%20these%20requirements%20for%20a%20specific%20tenant%20with%20low%20security%20requirements.%20If%20someone%20can%20point%20me%20in%20the%20right%20direction%20that%20would%20be%20great.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EMarco%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-188218%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAccess%20Management%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20AD%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-194550%22%20slang%3D%22en-US%22%3ERe%3A%20Default%20security%20settings%20for%20Office%20365%20for%20first%20account%20logon%20on%20new%20device%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-194550%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20but%20if%20we%20have%20it%20disabled%20via%20Intune%2C%20it%20still%20challenges%20to%20create%20a%20PIN.%20I%20have%20several%20customers%20who%20do%20not%20want%20to%20leverage%20a%20PIN%20and%20have%20Hello%20completely%20disabled%20and%20Windows%20STILL%20challenges%20us%20to%20create%20a%20pin%20on%20first%20login.%20This%20flies%20in%20the%20face%20of%20the%20intended%20config.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-188286%22%20slang%3D%22en-US%22%3ERe%3A%20Default%20security%20settings%20for%20Office%20365%20for%20first%20account%20logon%20on%20new%20device%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-188286%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Vasil%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%20So%20my%20preliminary%20conclusion%20was%20right.%20The%20PIN%20code%20triggers%20the%20MFA%20requirement.%20I%20just%20did%20not%20realize%20that%20the%20PIN%20code%20comes%20from%20Windows%20Hello%20for%20Business%20and%20you%20pointed%20me%20in%20the%20right%20direction.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EApparently%2C%20disabling%20Windows%20Hello%20for%20Business%20requires%20Intune%2C%20and%20cannot%20be%20done%20using%20the%20Office%20365%20built-in%20MDM%20device%20policies.%20When%20searching%20for%20%22office%20365%20disable%20windows%20hello%22%20I%20see%20a%20lot%20of%20disappointment%20that%20you%20need%20Intune%20to%20disable%20this%20behavior%20when%20exclusively%20using%20Azure%20AD%20joined%20devices.%20Microsoft%20requiring%20clients%20to%20spend%20money%20to%20disable%20a%20forcefully%20pushed%20security%20feature%3F%20Not%20the%20way%20to%20go%20I%20think%20for%20Microsoft.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWell%2C%20at%20least%20now%20I%20know%20and%20I%20can%20advise%20my%20client%20on%20the%20options%20available.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20again%2C%3C%2FP%3E%3CP%3EMarco%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-188282%22%20slang%3D%22en-US%22%3ERe%3A%20Default%20security%20settings%20for%20Office%20365%20for%20first%20account%20logon%20on%20new%20device%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-188282%22%20slang%3D%22en-US%22%3E%3CP%3EYup%2C%20they%20are%20connected.%20The%20PIN%20code%20requirement%20is%20enforced%20from%20the%20device%2C%20that's%20basically%20the%20%22gesture%22%20used%20for%20Windows%20Hello%20(or%20the%20fallback%20in%20this%20scenario).%20As%20this%20is%20considered%26nbsp%3Bvery%20sensitive%2C%20it%20triggers%20the%20MFA%20challenge%20as%20well.%20You%20can%20disable%20it%20via%20GPOs%20(not%20recommended)%20or%20you%20can%20use%20an%20Intune%20policy%20that%20does%20not%20require%20Windows%20Hello%20(and%20thus%20the%20MFA%20challenge)%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fintune-classic%2Fdeploy-use%2Fcontrol-microsoft-passport-settings-on-devices-with-microsoft-intune%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fintune-classic%2Fdeploy-use%2Fcontrol-microsoft-passport-settings-on-devices-with-microsoft-intune%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Marco de Bock
New Contributor

I am trying to figure out where to change the security settings on Office 365 when a user logs on to a new device for the first time.

 

Story: I created a new Office 365 tenant, added some standard users (no sync, just cloud users), leaving all settings at their defaults. This means no MFA, no extra device policy, etc. Then I joined a new / re-installed Windows 10 laptop to Azure AD by selecting 'this laptop is for work' in the OOBE (aka first run experience). Then, again using a standard user, I get two remarks regarding authentication:

 

  1. A PIN code is required for extra security at logon ("Your organization requires Windows Hello") > Set up PIN.
  2. The user needs to confirm its identity. ("Your admin has required that you set up this account for additional security verification") > Set it up now. Options are phone call, SMS or mobile app).

During testing, it seems that step 2 is a consequence of step 1. But I am not 100% sure. 

 

My question is: where do these requirements come from? I haven't set any of these settings. I looked 'everywhere' in the Office 365 admin portal and in the Azure Portal but could not find any setting that regulates this experience. For example:

 

  • AAD admin center > Devices > Device Settings > Require MFA to join devices: No (=default)
  • AAD admin center > Devices Password Reset > Registration > Require users to register when signing in: No (switched from the default yes, but as expected had no effect)

I tested this on two new tenants, with two laptops, and the experience was the same.

 

I want to disable these requirements for a specific tenant with low security requirements. If someone can point me in the right direction that would be great.

 

Thanks,

Marco

 

 

 

3 Replies
Solution

Yup, they are connected. The PIN code requirement is enforced from the device, that's basically the "gesture" used for Windows Hello (or the fallback in this scenario). As this is considered very sensitive, it triggers the MFA challenge as well. You can disable it via GPOs (not recommended) or you can use an Intune policy that does not require Windows Hello (and thus the MFA challenge): https://docs.microsoft.com/en-us/intune-classic/deploy-use/control-microsoft-passport-settings-on-de...

Hi Vasil,

 

Thanks! So my preliminary conclusion was right. The PIN code triggers the MFA requirement. I just did not realize that the PIN code comes from Windows Hello for Business and you pointed me in the right direction.

 

Apparently, disabling Windows Hello for Business requires Intune, and cannot be done using the Office 365 built-in MDM device policies. When searching for "office 365 disable windows hello" I see a lot of disappointment that you need Intune to disable this behavior when exclusively using Azure AD joined devices. Microsoft requiring clients to spend money to disable a forcefully pushed security feature? Not the way to go I think for Microsoft.

 

Well, at least now I know and I can advise my client on the options available.

 

Thanks again,

Marco

 

 

 

Yes, but if we have it disabled via Intune, it still challenges to create a PIN. I have several customers who do not want to leverage a PIN and have Hello completely disabled and Windows STILL challenges us to create a pin on first login. This flies in the face of the intended config. 

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
35 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies