Home
%3CLINGO-SUB%20id%3D%22lingo-sub-581720%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-581720%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20your%20example%20Alex%2C%20why%20are%20trusted%20locations%20being%20excluded%3F%20It%20feels%20like%20this%20is%20the%20wrong%20way%20round%20if%20you%20only%20want%20to%20allow%20MFA%20registration%20from%20a%20trusted%20location%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-581835%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-581835%22%20slang%3D%22en-US%22%3E%3CP%3EQuick%20comment%3A%20The%20link%20under%20%22%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20%23ffffff%3B%20color%3A%20%23333333%3B%20font-family%3A%20'SegoeUI'%2C'Lato'%2C'Helvetica%20Neue'%2CHelvetica%2CArial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E%20I%20am%20excited%20to%20announce%20the%20public%20preview%20of%20%3C%2FSPAN%3E%3CU%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20underline%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E%3CA%20style%3D%22background-color%3A%20transparent%3B%20box-sizing%3A%20border-box%3B%20color%3A%20%23146cac%3B%20text-decoration%3A%20underline%3B%22%20href%3D%22https%3A%2F%2Fgo.microsoft.com%2Ffwlink%2F%3Flinkid%3D2083106%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20AD%20conditional%20access%3C%2FA%3E%3C%2FU%3E%22%26nbsp%3B%20is%20pointing%20to%20another%20very%20exciting%20but%20different%20Azure%20AD%20feature.%3C%2FP%3E%0A%3CP%3EThe%20correct%20link%20to%20the%20conditional%20access%20for%20the%20combined%20MFA%2FSSPR%20registration%20is%3A%20%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fauthentication%2Fhowto-registration-mfa-sspr-combined%23conditional-access-policies-for-combined-registration%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fauthentication%2Fhowto-registration-mfa-sspr-combined%23conditional-access-policies-for-combined-registration%3C%2FA%3E%3C%2FFONT%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-582890%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-582890%22%20slang%3D%22en-US%22%3E%3CP%20style%3D%22text-align%3A%20left%3B%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F112651%22%20target%3D%22_blank%22%3E%40Phil%20Cook%3C%2FA%3E%26nbsp%3Bbecause%20the%20policy%20blocks%20access%20to%20the%20registration%20page.%20The%20rules%20of%20the%20policy%20is%20block%20access%20unless%20on%20a%20trusted%20network.%3C%2FP%3E%0A%3CP%20style%3D%22text-align%3A%20left%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22text-align%3A%20left%3B%22%3EYou%20cannot%20do%20an%20allow%20if%20on%20trusted%20network%20policy%20because%20a%20user%20not%20on%20the%20trusted%20network%20would%20not%20be%20subject%20to%20the%20policy%20and%20therefore%20would%20get%20access%20to%20the%20registration%20page.%20See%20%3CA%20href%3D%22https%3A%2F%2Fc7solutions.com%2F2019%2F05%2Fregister-for-azure-ad-mfa-from-on-premises-or-known-networks-only%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fc7solutions.com%2F2019%2F05%2Fregister-for-azure-ad-mfa-from-on-premises-or-known-networks-only%3C%2FA%3E%20which%20I%20wrote%20up%20last%20week%20on%20how%20to%20se%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3Et%20this%20up.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-566348%22%20slang%3D%22en-US%22%3EConditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-566348%22%20slang%3D%22en-US%22%3E%3CP%3EHowdy%20folks%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMore%20and%20more%20organizations%20are%20using%20Multi-Factor%20Authentication%20(MFA)%20to%20protect%20their%20access%20and%20self-service%20password%20reset%20(SSPR)%20to%20reduce%20support%20costs%20and%20empower%20their%20users%20to%20manage%20their%20credential%20recovery.%20Our%20internal%20studies%20show%20that%20customers%20can%20cut%20their%20risk%20of%20account%20compromise%20by%2099%25%20by%20enabling%20MFA%2C%20so%20we%E2%80%99re%20REALLY%20happy%20to%20see%20this%20growing%20trend.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWith%20this%20increasing%20usage%2C%20we%20also%20heard%20loud%20and%20clear%20that%20you%20want%20to%20control%20the%20conditions%20in%20which%20security%20sensitive%20MFA%20or%20SSPR%20information%20can%20be%20registered.%20This%20helps%20ensure%20it%E2%80%99s%20the%20right%20user%E2%80%94not%20an%20attacker%E2%80%94registering%20this%20security%20sensitive%20info.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESome%20common%20restrictions%20you%20requested%20include%20ensuring%20that%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CUL%3E%3CLI%3EUsers%20are%20on%20a%20%3CSTRONG%3Etrusted%20network%3C%2FSTRONG%3E.%3C%2FLI%3E%3CLI%3EOnly%20users%20with%20a%20low%20%3CSTRONG%3Esign-in%20risk%20%3C%2FSTRONG%3Ecan%20register%20security%20information.%3C%2FLI%3E%3CLI%3EUsers%20can%20only%20register%20on%20a%20%3CSTRONG%3Emanaged%20device%3C%2FSTRONG%3E.%3C%2FLI%3E%3CLI%3EUsers%20should%20agree%20to%20a%20%3CSTRONG%3Eterms%20of%20use%3C%2FSTRONG%3E%20during%20registration.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CBR%20%2F%3EWe%20heard%20you%20loud%20and%20clear!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EToday%2C%20I%20am%20excited%20to%20announce%20the%20public%20preview%20of%20%3CU%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fauthentication%2Fhowto-registration-mfa-sspr-combined%23conditional-access-policies-for-combined-registration%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20AD%20conditional%20access%3C%2FA%3E%3C%2FU%3E%20for%20our%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FAzure-Active-Directory-Identity%2FCool-enhancements-to-the-Azure-AD-combined-MFA-and-password%2Fba-p%2F354271%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Ecombined%20registration%20experience%20for%20MFA%20and%20SSPR%3C%2FA%3E%3C%2FSPAN%3E.%20Many%20of%20our%20largest%20customers%20have%20already%20been%20using%20this%20while%20it%20was%20in%20private%20preview%20to%20simplify%20rolling%20out%20MFA%20and%20SSPR%20and%20we%E2%80%99re%20looking%20forward%20to%20making%20it%20more%20broadly%20available%20as%20part%20of%20Azure%20AD%20Premium%20P1%20subscription.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20are%20some%20instructions%20to%20try%20this%20out!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%224%22%3E%3CFONT%20size%3D%225%22%3EGetting%20started%3C%2FFONT%3E%3CSTRONG%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3EFirst%2C%20create%20a%20policy%20to%20block%20registration%20for%20users%20that%20are%20not%20on%20the%20corporate%20network%2C%20but%20are%20still%20allowed%20to%20manage%20credentials%20from%20anywhere%2C%20as%20long%20as%20they%20can%20use%20MFA.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENext%2C%20make%20sure%20that%20all%20users%20you%20want%20to%20apply%20this%20policy%20to%20are%20part%20of%20the%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FAzure-Active-Directory-Identity%2FCool-enhancements-to-the-Azure-AD-combined-MFA-and-password%2Fba-p%2F354271%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3EMFA%20and%20SSPR%20preview%3C%2FA%3E%3C%2FSPAN%3E.%20This%20is%20required%20because%20users%20not%20on%20the%20preview%20will%20use%20the%20older%20security%20information%20page%20and%20the%20policy%20will%20not%20be%20enforced.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3ESteps%20for%20setting%20up%20policy%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3EInclude%20the%20users%20the%20policy%20will%20apply%20to%20using%20the%20%3CSTRONG%3EUsers%20and%20groups%3C%2FSTRONG%3E.%3C%2FLI%3E%3CLI%3EApply%20policy%20to%20the%20%3CSTRONG%3ERegister%20security%20information%3C%2FSTRONG%3E%20action%2C%20which%20is%20now%20included%20in%20the%20%3CSTRONG%3ECloud%20apps%20or%3C%2FSTRONG%3E%20%3CSTRONG%3Eactions%3C%2FSTRONG%3E.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20624px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F113778i2083776296700193%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Conditional%20Access%20for%20the%20Azure%20AD%201.png%22%20title%3D%22Conditional%20Access%20for%20the%20Azure%20AD%201.png%22%20%2F%3E%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLI%3E%3CLI%3E%3CP%3ESet%20the%20%3CSTRONG%3ELocations%3C%2FSTRONG%3E.%20Include%20%3CSTRONG%3EAny%20location%3B%20exclude%20all%20trusted%20networks%3C%2FSTRONG%3E%3CEM%3E.%3C%2FEM%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3ESet%20the%20access%20grant%20control%20to%20%3CSTRONG%3Erequire%20multi-factor%20authentication%3C%2FSTRONG%3E%3CEM%3E.%3C%2FEM%3E%3C%2FLI%3E%3CLI%3EEnable%20policy%20and%20%3CSTRONG%3ESave%3C%2FSTRONG%3E.%3C%2FLI%3E%3C%2FOL%3E%3CP%3E%3CBR%20%2F%3ENow%2C%20if%20a%20user%20is%20outside%20of%20a%20trusted%20network%20and%20attempts%20to%20register%20MFA%20for%20the%20first%20time%2C%20they%E2%80%99re%20blocked%20and%20shown%20the%20following%20message%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20424px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F113779iD815E29825613E69%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Conditional%20Access%20for%20the%20Azure%20AD%202.png%22%20title%3D%22Conditional%20Access%20for%20the%20Azure%20AD%202.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20soon%20as%20they%20register%20MFA%2C%20they%E2%80%99ll%20be%20able%20to%20manage%20MFA%20and%20SSPR%20registration%20details%20from%20anywhere.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGo%20ahead%20and%20give%20it%20try%20today!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESee%20our%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FCAActionsDoc%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20AD%20conditional%20access%20documentation%3C%2FA%3E%3C%2FSPAN%3E%20for%20additional%20information.%20We%E2%80%99d%20also%20love%20to%20hear%20your%20feedback.%20If%20you%20have%20a%20couple%20minutes%20please%20consider%20filling%20out%20our%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FCAActionSurvey%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Esurvey%3C%2FA%3E%3C%2FSPAN%3E.%20You%20know%20we%E2%80%99re%20listening!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20regards%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlex%20Simons%20(Twitter%3A%26nbsp%3B%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftwitter.com%2FAlex_A_Simons%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%40Alex_A_Simons%3C%2FA%3E%3C%2FSPAN%3E)%3CBR%20%2F%3EVice%20President%20of%20Program%20Management%3CBR%20%2F%3EMicrosoft%20Identity%20Division%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-566348%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20can%20now%20take%20full%20control%20of%20the%20conditions%20in%20which%20security%20sensitive%20MFA%20or%20SSPR%20information%20can%20be%20registered!%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-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-566348%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Active%20Directory%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIdentity%20and%20Access%20Management%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-622584%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-622584%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20sounds%20promising!%20Since%20you%20mentioned%20a%20few%20examples%20I%20guess%20you%20have%20it%20on%20the%20roadmap.%20Can%20you%20share%20any%20more%20information%20on%20when%20it%20will%20be%20possible%20to%20require%20users%20to%20accept%20terms%20of%20use%2C%20and%20to%20require%20managed%20devices%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-623316%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-623316%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20it%20possible%20to%20do%20the%20same%2C%20but%20when%20the%20user%20is%20already%20registered%3F%3C%2FP%3E%3CP%3EMeaning%2C%20if%20I%20want%20to%20force%20all%20of%20my%20users%20to%20use%20Authenticator%20App%20instead%20of%20sms%20or%20calls..%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-632460%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-632460%22%20slang%3D%22en-US%22%3E%3CP%3ENice!%20We%20are%20already%20using%20the%20new%20portal%20and%20to%20be%20able%20to%20lock%20down%20MFA%20enrollment%20is%20perfect.%26nbsp%3B%3C%2FP%3E%3CP%3EAccess%20is%20blocked%20as%20expected%20from%20an%20untrusted%20device%20but%20from%20this%20device%20we%20are%20still%20able%20to%20enroll%20for%20MFA%20when%20using%20Word.%20If%20you%20add%20an%20account%20in%20Word%20from%20an%20untrusted%20device%20with%20a%20new%20user%20account%20(our%20CA%20policy%20needs%20MFA%20or%20hybrid%20joined%20deviced%20or%20compliant%20device)%20it%20tells%20the%20user%20to%20enroll%20for%20MFA%20and%20this%20works%20from%20word%20but%20not%20from%20the%20browser.%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20idea%20how%20to%20fix%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-666259%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-666259%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F345559%22%20target%3D%22_blank%22%3E%40mattiasnyholm%3C%2FA%3E%2C%20these%20examples%20are%20possible%20today%20using%20the%20preview.%20Instead%20of%20requiring%20MFA%20as%20the%20required%20access%20control%20just%20pick%20a%20terms%20of%20use%20page%20or%20require%20a%20compliant%20device.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-666261%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-666261%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F330545%22%20target%3D%22_blank%22%3E%40andrii_ua%3C%2FA%3E%2C%20that's%20outside%20of%20this%20feature%2C%20but%20on%20the%20roadmap.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-666269%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-666269%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22lia-message-author-with-avatar%22%3E%3CSPAN%20class%3D%22UserName%20lia-user-name%20lia-user-rank-Visitor%20lia-component-message-view-widget-author-username%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F221400%22%20target%3D%22_blank%22%3E%40Rolf%20Troendle%3C%2FA%3E%2C%20I%20just%20tried%20to%20reproduce%20this%20using%20Office%20ProPlus%20and%20wasn't%20able%20to.%20Let%20me%20know%20if%20you%20are%20still%20seeing%20this%20and%20we%20can%20take%20a%20look.%20%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-686878%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-686878%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F353454%22%20target%3D%22_blank%22%3E%40caleb_b%3C%2FA%3E%26nbsp%3B%20Thank%20you%20for%20your%20reply.%20I%20have%20just%20tried%20it%20again%20and%20I%20was%20blocked%20by%20CA%20-%20so%20everything%20is%20fine%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-691763%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-691763%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20it%20possible%20to%20use%20CA%20to%20only%20allow%20password%20resets%20from%20a%20trusted%20network%3F%20I%20can't%20seem%20to%20find%20this%20anywhere.%20The%20above%20allows%20registration%20from%20a%20trusted%20network%20only%2C%20we'd%20love%20to%20go%20one%20step%20further%20and%20only%20allow%20the%20use%20of%20SSPR%20from%20the%20trusted%20network%20as%20well.%3CBR%20%2F%3E%3CBR%20%2F%3EAnyone%20seen%20or%20done%20anything%20like%20this%20before%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-695308%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-695308%22%20slang%3D%22en-US%22%3E%3CP%3EIts%20possible%20to%20bypass%20the%20MFA%20setup%20block%20with%20the%20new%20%22Baseline%20policy%3A%20End%20user%20protection%22%20policy.%20If%20you%20click%20%22%3CA%20href%3D%22https%3A%2F%2Flogin.microsoftonline.com%2Fcommon%2Freprocess%3Fctx%3DrQIIAYWSvW_TQADF43zRlBaqToipSExISexz7NZBlWjz0bjNnZM0TnAGosQ5J3bis-tcksYjEoixcyUWxo4gIaj4A1DFUDEwVDCAGBATQh1YkEjEwsYbnt7whif93p0Ql-DSt9m_EuNzj7OGwcV1PE__yFtdXLn78m37xdcH8qPLi8eBT28-nzC3epS6w3Qy6ToebQ0SjmGYOk7ojp0ctEjHJN1XDHPOMN8Y5jgYwSSu7p8EhyIvSiIviBsiz6UkAWxICQ3IE2ip04alUlRv9JHJsrCqTYrVLgsBpMrOrol8ZCNfFlB10NPsnKBVy5wGyhT6sg-nLKtkZb9YHdgo26cw2zAhQH3N76caVchfBK8rWyPaA3NzPNPHP4Mxw_HspusM6XHoPaO4mMidjEMI1mliXsOEmnqLmg4peY6LPWri4WbWGBtqvGATRKSMKuTrci1THgGwHuf3YKpYrrQ3fH86wKO9sboPAHsgFOsTo88rJDNGE8leBxhmpENhV6KVNtzd9rw8l7X0kVezO6DUzZn50v4A1QG0WlqnWRR3tohT3YpDLcOLtRKetA8s2ETD2tQ2BdBSOEXjDC8_HgkA5tyKTe8jC6CStq25-vNQdAbCdshZ6NpsPzE7a67nGOYAfwndtI0WxUN6b9ZwRxR7esubc0sQ_zzMfA8vsaH0wsLiSuBGYC3wK8w8i8z4hyPLeoCtFJ8eXL573WwGziLJnAUyXanQL2YPawa_Xe76CMj9pEp4Lq9x7Y5UwvKkXuhlSWoTpLmjKHMUjf6IBp9cYU5j_3_Pw6XlhcBqLPbxKjz9_fND4Q81%26amp%3Bskipmfaregistration%3D1%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESkip%20for%20now%20(14%20days%20until%20this%20is%20required)%3C%2FA%3E%22%20box%20it%20will%20successfully%20log%20you%20into%20the%20Office%20365%20portal%20without%20requiring%20MFA%20setup%2C%20or%20blocking%20access.%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-720654%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-720654%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20i've%20created%20a%20policy%20just%20to%20test%20this%20and%20I%20can't%20get%20it%20to%20work%20on%20my%20own%20account.%3C%2FP%3E%3CP%3EDoes%20this%20only%20apply%20the%20%3CEM%3Every%26nbsp%3Bfirst%3C%2FEM%3E%20time%20a%20user%20enrolls%20their%20MFA%3F%20As%20in%2C%20i've%20destroyed%20my%20app's%20token%20for%20this%20tenant%20and%20attempted%20to%20re-register%20my%20MFA%20details%20through%20the%20normal%20process%20from%20different%20un-trusted%20networks%20and%20it%20does%20not%20prevent%20me%20re-registering%20my%20MFA.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20set%20up%20the%20policy%20exactly%20as%20described%20above%20but%20when%20I%20audit%20the%20sign-in%2C%20the%20conditional%20access%20policy%20is%20not%20triggered%20at%20all%20no%20matter%20which%20network%20i%20attempt%20to%20re-register%20from.%20Appreciate%20any%20ideas%20you%20may%20have%3F%3C%2FP%3E%3CP%3ECheers%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-721108%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-721108%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F366627%22%20target%3D%22_blank%22%3E%40JonYoung%3C%2FA%3E%26nbsp%3Bcheck%20your%20settings%20against%20%3CA%20href%3D%22https%3A%2F%2Fc7solutions.com%2F2019%2F05%2Fregister-For-Azure-AD-MFA-From-On-Premises-Or-Known-Networks-only%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fc7solutions.com%2F2019%2F05%2Fregister-For-Azure-AD-MFA-From-On-Premises-Or-Known-Networks-only%3C%2FA%3E%20as%20those%20work%20perfectly.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-722832%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-722832%22%20slang%3D%22en-US%22%3E%3CP%3EBeautiful%2C%20thanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F157%22%20target%3D%22_blank%22%3E%40Brian%20Reid%3C%2FA%3E.%20Working%20nicely%20after%20I%20enabled%20the%20access%20panel%20preview%20features.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-723762%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-723762%22%20slang%3D%22en-US%22%3E%3CP%3EYes%20-%20MFA%20registration%20blocks%20only%20work%20against%20the%20latest%20registration%20page%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-728294%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-728294%22%20slang%3D%22en-US%22%3EHello%2C%20I%20followed%20your%20instruction%20to%20enforce%20MFA%20registration%20with%20a%20trusted%20network%20only.%20It%20is%20working%20well%2C%20user%20is%20well%20blocked%20when%20accessing%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fmfasetup%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fmfasetup%3C%2FA%3E%20from%20an%20untrusted%20network.%20However%20a%20user%2C%20without%20MFA%20registered%2C%20can%20still%20enroll%20a%20new%20device%20in%20Intune%20(MFA%20is%20required)%20on%20an%20untrusted%20network%20and%20it%20will%20ask%20him%20to%20set%20up%20his%20account%20for%20additional%20security%20verification.%20Then%20he%20is%20able%20to%20setup%20the%20MFA%20on%20this%20untrusted%20network.%20Thanks%20for%20your%20feedback%20on%20this%20Guillaume%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-840792%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-840792%22%20slang%3D%22en-US%22%3E%3CP%3EDid%20anything%20break%20in%20this%20condition%20lately%3F%3C%2FP%3E%3CP%3EIt%20used%20to%20work%20before%2C%20but%20now%2C%20even%20when%20I%20set%20a%20condition%20to%20block%20registration%20from%20Any%20network%20even%2C%20it%20just%20nicely%20continues%20to%20the%20registration%20page.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-842173%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-842173%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F53477%22%20target%3D%22_blank%22%3E%40Alex%20Simons%20(AZURE)%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F187075%22%20target%3D%22_blank%22%3E%40Sadie%20Henry%3C%2FA%3E%26nbsp%3BI%20read%20in%20the%20Azure%20update%20notice%20that%20this%20enhanced%20registration%20wizard%20is%20going%20out%20of%20preview%20on%20Setp%2025th.%20Does%20this%20just%20replace%20the%20earlier%20preview%20that%20has%20been%20around%20two%20or%20so%20years%20or%20both%20it%20and%20the%20original%20registration%20process%20that%20has%20been%20in%20Azure%20AD%20for%20almost%20since%20it%20started%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-852689%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-852689%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F157%22%20target%3D%22_blank%22%3E%40Brian%20Reid%3C%2FA%3E%26nbsp%3BI%20wonder%20this%20too.%20Where%20did%20you%20actually%20see%20this%20announcement%20in%20your%20tenant%3F%20I%20want%20to%20check%20it%20too%20for%20our%20customer%E2%80%99s%20tenant%20since%20we%E2%80%99re%20right%20now%20rolling%20it%20out%20to%2010.000%2B%20users%20and%20making%20it%20GA%20is%20definitely%20something%20that%20would%20make%20it%20easier%20from%20a%20support%20perspective.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-854272%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-854272%22%20slang%3D%22en-US%22%3E%3CP%3EJonas%20-%20no%20announcement%20in%20the%20tenant.%20There%20was%20an%20email%20to%20affected%20Admins%20and%20the%20notice%20was%20in%20the%20What's%20New%20in%20Azure%20AD%20blog%20page.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESadie%20on%20Twitter%20said%20that%20the%20settings%20for%20the%20original%20preview%20are%20merged%20with%20the%20new%20preview%20on%2025th.%20It%20does%20not%20affect%20the%20original%20registration%20wizard%20at%20this%20time%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856537%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856537%22%20slang%3D%22en-US%22%3EGood%20morning%20Is%20there%20a%20way%20to%20let%20the%20user%20opt-in%20for%20MFA%20at%20his%20earliest%20convenience%20if%20within%20a%20grace%20period%20%3F%20I%20try%20to%20explain%20the%20scope.%20I'm%20going%20to%20enable%20MFA%20for%20a%20large%20number%20of%20users%2C%20however%20I%20want%20to%20give%20them%2040%20days%20to%20self-register%20for%20MFA.%20After%20that%20period%20all%20users%20will%20be%20enabled%20in%20a%20bounce.%201)%20I%20cannot%20do%20it%20enabling%20them%20in%20Office365%20admin%20page%20otherwise%20they%20will%20receive%20immediately%20a%20MFA%20request%20as%20soon%20as%20they%20access%20any%20Office365%20Application.%202)%20If%20they%20are%20not%20enabled%20and%20they%20go%20to%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fmfasetup%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fmfasetup%3C%2FA%3E%20they%20register%20only%20the%20security%20info%20and%20after%20that%20MFA%2C%20is%20requested%20only%20if%20you%20access%20again%20the%20mfasetup%20and%20nothing%20is%20requested%20for%20the%20other%20O365%20resources.%203)%20Is%20there%20a%20way%20to%20activate%20MFA%20for%20all%20O365%20when%20you%20register%20your%20info%20on%20mfasetup%20page%20%3F%20Maybe%20with%20a%20conditional%20access%20when%20you%20visit%20a%20specific%20url%20%3F%20Thanks%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856586%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856586%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F409341%22%20target%3D%22_blank%22%3E%40Chris2705%3C%2FA%3E%3A%20yes%20it%20is%20for%2014%20days%20with%20%22Multi-factor%20authentication%20registration%20policy%22.%2014%20days%20is%20not%20configurable%20and%20you%20need%20Azure%20AD%20Premium%20P2%20for%20this%20policy.%3C%2FP%3E%3CP%3EWhat%20we%20have%20done%20is%20telling%20the%20users%20to%20pre-register%20during%20the%20next%2014%20days%20and%20afterwards%20we%20enforced%20it%20using%20CA.%3C%2FP%3E%3CP%3EReference%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fidentity-protection%2Fflows%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fidentity-protection%2Fflows%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856666%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856666%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F409341%22%20target%3D%22_blank%22%3E%40Chris2705%3C%2FA%3E%26nbsp%3Bthe%20new%20(in%20preview)%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3E%26nbsp%3Bfeature%20of%26nbsp%3B%20%22Baseline%20Policy%3A%20End%20user%20protection%22%20also%20does%20this.%2014%20registration%20window%20and%20implements%20MFA%20on%20a%20risky%20sign%20in.%20Impacts%20all%20users%2C%20including%20break%20glass%20accounts%20(unfortunately%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F53477%22%20target%3D%22_blank%22%3E%40Alex%20Simons%20(AZURE)%3C%2FA%3E)%20but%20does%20not%20require%20AADP2%20license%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-889414%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-889414%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F53477%22%20target%3D%22_blank%22%3E%40Alex%20Simons%20(AZURE)%3C%2FA%3E%20Can%20you%20clarify%20a%20detail%20about%20this%20capabilty.%20After%20implmenting%20a%20CA%20rule%20to%20block%20registration%20from%20outside%20our%20internal%20network%2C%20would%20the%20same%20CA%20rule%20prevent%20the%20user%20from%20updating%20their%20contact%20information%20from%20outside%20the%20network%3F%20The%20distinstinction%20here%20is%20an%20intitial%20setup%20vs%20and%20update%20to%20existing%20information%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-889552%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-889552%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F102408%22%20target%3D%22_blank%22%3E%40Manoj%20Sood%3C%2FA%3E%20%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3EThis%20capability%20will%20apply%20to%20registering%20and%20managing%20strong%20authentication%20information.%20This%20includes%20the%20phone%20number%20used%20for%20strong%20authentication.%20It%20doesn't%20cover%20contact%20info.%20The%20phone%20number%20a%20user%20would%20register%20for%20contact%20info%20is%20stored%20separately%20than%20the%20number%20they%20would%20register%20for%20strong%20auth.%20So%20this%20policy%20will%20not%20impact%20updates%20to%20contact%20info.%20The%20strong%20auth%20and%20contact%20phone%20number%20are%20stored%20separately%20for%20a%20variety%20of%20security%20and%20privacy%20reasons.%20For%20example%2C%20just%20because%20somebody%20registers%20a%20phone%20number%20for%20strong%20auth%20it%20doesn't%20mean%20they%20want%20it%20published%20to%20their%20organization%20as%20contact%20info.%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-889556%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-889556%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F102408%22%20target%3D%22_blank%22%3E%40Manoj%20Sood%3C%2FA%3E%26nbsp%3Bthe%20CA%20rule%20can%20be%20used%20to%20block%20registration%20only.%20Once%20you%20have%20registered%20further%20updates%20are%20not%20blocked%20because%20once%20you%20have%20registered%20you%20need%20to%20use%20MFA%20to%20make%20any%20changes%20to%20your%20MFA%20settings%20(and%20as%20mentioned%20above%2C%20these%20are%20not%20your%20contact%20details).%20If%20your%20IT%20department%20resets%20your%20registration%20you%20will%20need%20to%20be%20in%20scope%20of%20the%20CA%20rule%2C%20but%20only%20to%20register%20again.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-889596%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-889596%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F353454%22%20target%3D%22_blank%22%3E%40caleb_b%3C%2FA%3E%20Thanks%20for%20the%20reply.%20I%20should%20have%20been%20a%20little%20more%20specific%20in%20my%20question.%20The%20%22contact%20info%22%20I%20was%20referring%20to%20is%20%22Authentication%20Contact%20Info%22%20found%20on%20the%20users%20AAD%20account%20in%20the%20%22Authentication%20methods%22%20blade.%20This%20contact%20info%20is%20not%20published%20as%20part%20of%20any%20organizational%20contact%20info%20that%20I%20am%20aware%20of.%20Scenario%3A%20CA%20policy%20prevents%20user%20from%20initial%20registration%20outside%20corp%20network.%20User%20gets%20new%20phone%20and%20is%20unable%20to%20receive%20SMS%20message%20for%20SSPR%20until%20info%20is%20updated.%20The%20same%20reasons%20for%20not%20wanting%20users%20to%20do%20their%20initial%20registration%20apply%20to%20preventing%20users%20from%20updating%20their%20Authentication%20contact%20Info%20from%20off%20the%20corp%20network.%20Should%20a%20CA%20rule%20blocking%20user%20registration%20also%20block%20updating%20info%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-889608%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-889608%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%0A%3CP%3EUser%20gets%20new%20phone%20and%20is%20unable%20to%20receive%20SMS%20message%20for%20SSPR%20until%20info%20is%20updated%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F102408%22%20target%3D%22_blank%22%3E%40Manoj%20Sood%3C%2FA%3E%26nbsp%3BOnly%20if%20the%20phone%20number%20on%20the%20new%20phone%20has%20changed.%20If%20its%20the%20same%20number%20then%20SMS%20will%20work.%3C%2FP%3E%0A%3CP%3EAs%20I%20mentioned%20above%2C%20updates%20are%20not%20registration.%20You%20can%20update%20from%20wherever%20because%20you%20have%20to%20do%20an%20MFA%20proof%20to%20get%20to%20the%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fmfasetup%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fmfasetup%3C%2FA%3E%20page.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-889630%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-889630%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F157%22%20target%3D%22_blank%22%3E%40Brian%20Reid%3C%2FA%3E%20My%20scenario%20was%20%22User%20gets%20new%20phone%20and%20is%20unable%20to%20receive%20SMS%20message%22%20so%20a%20new%20number%20would%20be%20involved.%20You%20of%20course%20correct%20that%20a%20new%20phone%20with%20the%20same%20number%20would%20not%20have%20an%20issue.%20Bottomline%20is%20that%20updates%20are%20not%20blocked%20by%20CA%20rule.%20Thanks%20for%20clarifying%20that%20for%20me.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-979210%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20for%20the%20Azure%20AD%20combined%20MFA%20and%20password%20reset%20registration%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-979210%22%20slang%3D%22en-US%22%3E%3CP%3Ei%20have%20already%20registered%20for%20MFA%2C%20now%20i%20want%20to%20block%20the%20registration%20MFA%20setup%20from%20Un%20trust%20network..%20i%20have%20implement%20the%20same%2C%20but%20still%20allows%20after%20the%20authentication%20with%20MFA%3C%2FP%3E%3C%2FLINGO-BODY%3E

Howdy folks,

 

More and more organizations are using Multi-Factor Authentication (MFA) to protect their access and self-service password reset (SSPR) to reduce support costs and empower their users to manage their credential recovery. Our internal studies show that customers can cut their risk of account compromise by 99% by enabling MFA, so we’re REALLY happy to see this growing trend.

 

With this increasing usage, we also heard loud and clear that you want to control the conditions in which security sensitive MFA or SSPR information can be registered. This helps ensure it’s the right user—not an attacker—registering this security sensitive info.

 

Some common restrictions you requested include ensuring that:

  • Users are on a trusted network.
  • Only users with a low sign-in risk can register security information.
  • Users can only register on a managed device.
  • Users should agree to a terms of use during registration.


We heard you loud and clear!

 

Today, I am excited to announce the public preview of Azure AD conditional access for our combined registration experience for MFA and SSPR. Many of our largest customers have already been using this while it was in private preview to simplify rolling out MFA and SSPR and we’re looking forward to making it more broadly available as part of Azure AD Premium P1 subscription.

 

Here are some instructions to try this out!

 

Getting started

First, create a policy to block registration for users that are not on the corporate network, but are still allowed to manage credentials from anywhere, as long as they can use MFA.

 

Next, make sure that all users you want to apply this policy to are part of the MFA and SSPR preview. This is required because users not on the preview will use the older security information page and the policy will not be enforced.

 

Steps for setting up policy

 

  1. Include the users the policy will apply to using the Users and groups.
  2. Apply policy to the Register security information action, which is now included in the Cloud apps or actions.

    Conditional Access for the Azure AD 1.png

  3. Set the Locations. Include Any location; exclude all trusted networks.

  4. Set the access grant control to require multi-factor authentication.
  5. Enable policy and Save.


Now, if a user is outside of a trusted network and attempts to register MFA for the first time, they’re blocked and shown the following message:

 

Conditional Access for the Azure AD 2.png

 

As soon as they register MFA, they’ll be able to manage MFA and SSPR registration details from anywhere.

 

Go ahead and give it try today!

 

See our Azure AD conditional access documentation for additional information. We’d also love to hear your feedback. If you have a couple minutes please consider filling out our survey. You know we’re listening!

 

Best regards,

 

Alex Simons (Twitter: @Alex_A_Simons)
Vice President of Program Management
Microsoft Identity Division

31 Comments
New Contributor

In your example Alex, why are trusted locations being excluded? It feels like this is the wrong way round if you only want to allow MFA registration from a trusted location?

Microsoft

Quick comment: The link under " I am excited to announce the public preview of Azure AD conditional access"  is pointing to another very exciting but different Azure AD feature.

The correct link to the conditional access for the combined MFA/SSPR registration is: https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-registration-mfa-sspr-c... 

@Phil Cook because the policy blocks access to the registration page. The rules of the policy is block access unless on a trusted network.

 

You cannot do an allow if on trusted network policy because a user not on the trusted network would not be subject to the policy and therefore would get access to the registration page. See https://c7solutions.com/2019/05/register-for-azure-ad-mfa-from-on-premises-or-known-networks-only which I wrote up last week on how to set this up. 

Frequent Visitor

This sounds promising! Since you mentioned a few examples I guess you have it on the roadmap. Can you share any more information on when it will be possible to require users to accept terms of use, and to require managed devices?

Senior Member

Is it possible to do the same, but when the user is already registered?

Meaning, if I want to force all of my users to use Authenticator App instead of sms or calls.. ?

Established Member

Nice! We are already using the new portal and to be able to lock down MFA enrollment is perfect. 

Access is blocked as expected from an untrusted device but from this device we are still able to enroll for MFA when using Word. If you add an account in Word from an untrusted device with a new user account (our CA policy needs MFA or hybrid joined deviced or compliant device) it tells the user to enroll for MFA and this works from word but not from the browser. 

Any idea how to fix this?

Frequent Visitor

@mattiasnyholm, these examples are possible today using the preview. Instead of requiring MFA as the required access control just pick a terms of use page or require a compliant device.

 

Frequent Visitor

@andrii_ua, that's outside of this feature, but on the roadmap.

Frequent Visitor

 

@Rolf Troendle, I just tried to reproduce this using Office ProPlus and wasn't able to. Let me know if you are still seeing this and we can take a look.
Established Member

@caleb_b  Thank you for your reply. I have just tried it again and I was blocked by CA - so everything is fine

New Contributor

Is it possible to use CA to only allow password resets from a trusted network? I can't seem to find this anywhere. The above allows registration from a trusted network only, we'd love to go one step further and only allow the use of SSPR from the trusted network as well.

Anyone seen or done anything like this before?

Occasional Visitor

Its possible to bypass the MFA setup block with the new "Baseline policy: End user protection" policy. If you click "Skip for now (14 days until this is required)" box it will successfully log you into the Office 365 portal without requiring MFA setup, or blocking access.

 

 

Frequent Visitor

Hi, i've created a policy just to test this and I can't get it to work on my own account.

Does this only apply the very first time a user enrolls their MFA? As in, i've destroyed my app's token for this tenant and attempted to re-register my MFA details through the normal process from different un-trusted networks and it does not prevent me re-registering my MFA.

 

I've set up the policy exactly as described above but when I audit the sign-in, the conditional access policy is not triggered at all no matter which network i attempt to re-register from. Appreciate any ideas you may have?

Cheers

Frequent Visitor

Beautiful, thanks @Brian Reid. Working nicely after I enabled the access panel preview features.

Yes - MFA registration blocks only work against the latest registration page

Frequent Visitor
Hello, I followed your instruction to enforce MFA registration with a trusted network only. It is working well, user is well blocked when accessing https://aka.ms/mfasetup from an untrusted network. However a user, without MFA registered, can still enroll a new device in Intune (MFA is required) on an untrusted network and it will ask him to set up his account for additional security verification. Then he is able to setup the MFA on this untrusted network. Thanks for your feedback on this Guillaume
New Contributor

Did anything break in this condition lately?

It used to work before, but now, even when I set a condition to block registration from Any network even, it just nicely continues to the registration page.

@Alex Simons (AZURE) @Sadie Henry I read in the Azure update notice that this enhanced registration wizard is going out of preview on Setp 25th. Does this just replace the earlier preview that has been around two or so years or both it and the original registration process that has been in Azure AD for almost since it started? 

Frequent Contributor

@Brian Reid I wonder this too. Where did you actually see this announcement in your tenant? I want to check it too for our customer’s tenant since we’re right now rolling it out to 10.000+ users and making it GA is definitely something that would make it easier from a support perspective.

Jonas - no announcement in the tenant. There was an email to affected Admins and the notice was in the What's New in Azure AD blog page.

 

Sadie on Twitter said that the settings for the original preview are merged with the new preview on 25th. It does not affect the original registration wizard at this time

Occasional Visitor
Good morning Is there a way to let the user opt-in for MFA at his earliest convenience if within a grace period ? I try to explain the scope. I'm going to enable MFA for a large number of users, however I want to give them 40 days to self-register for MFA. After that period all users will be enabled in a bounce. 1) I cannot do it enabling them in Office365 admin page otherwise they will receive immediately a MFA request as soon as they access any Office365 Application. 2) If they are not enabled and they go to https://aka.ms/mfasetup they register only the security info and after that MFA, is requested only if you access again the mfasetup and nothing is requested for the other O365 resources. 3) Is there a way to activate MFA for all O365 when you register your info on mfasetup page ? Maybe with a conditional access when you visit a specific url ? Thanks
Established Member

@Chris2705: yes it is for 14 days with "Multi-factor authentication registration policy". 14 days is not configurable and you need Azure AD Premium P2 for this policy.

What we have done is telling the users to pre-register during the next 14 days and afterwards we enforced it using CA.

Reference: https://docs.microsoft.com/en-us/azure/active-directory/identity-protection/flows

 

@Chris2705 the new (in preview) feature of  "Baseline Policy: End user protection" also does this. 14 registration window and implements MFA on a risky sign in. Impacts all users, including break glass accounts (unfortunately @Alex Simons (AZURE)) but does not require AADP2 license 

Occasional Contributor
@Alex Simons (AZURE) Can you clarify a detail about this capabilty. After implmenting a CA rule to block registration from outside our internal network, would the same CA rule prevent the user from updating their contact information from outside the network? The distinstinction here is an intitial setup vs and update to existing information?
Frequent Visitor

Hi @Manoj Sood ,

 

This capability will apply to registering and managing strong authentication information. This includes the phone number used for strong authentication. It doesn't cover contact info. The phone number a user would register for contact info is stored separately than the number they would register for strong auth. So this policy will not impact updates to contact info. The strong auth and contact phone number are stored separately for a variety of security and privacy reasons. For example, just because somebody registers a phone number for strong auth it doesn't mean they want it published to their organization as contact info.

@Manoj Sood the CA rule can be used to block registration only. Once you have registered further updates are not blocked because once you have registered you need to use MFA to make any changes to your MFA settings (and as mentioned above, these are not your contact details). If your IT department resets your registration you will need to be in scope of the CA rule, but only to register again. 

Occasional Contributor
@caleb_b Thanks for the reply. I should have been a little more specific in my question. The "contact info" I was referring to is "Authentication Contact Info" found on the users AAD account in the "Authentication methods" blade. This contact info is not published as part of any organizational contact info that I am aware of. Scenario: CA policy prevents user from initial registration outside corp network. User gets new phone and is unable to receive SMS message for SSPR until info is updated. The same reasons for not wanting users to do their initial registration apply to preventing users from updating their Authentication contact Info from off the corp network. Should a CA rule blocking user registration also block updating info?

User gets new phone and is unable to receive SMS message for SSPR until info is updated

@Manoj Sood Only if the phone number on the new phone has changed. If its the same number then SMS will work.

As I mentioned above, updates are not registration. You can update from wherever because you have to do an MFA proof to get to the https://aka.ms/mfasetup page. 

Occasional Contributor
@Brian Reid My scenario was "User gets new phone and is unable to receive SMS message" so a new number would be involved. You of course correct that a new phone with the same number would not have an issue. Bottomline is that updates are not blocked by CA rule. Thanks for clarifying that for me.

i have already registered for MFA, now i want to block the registration MFA setup from Un trust network.. i have implement the same, but still allows after the authentication with MFA