Identity
66 TopicsHow to disable option to stay signed in
The option for users to choose to stay signed in to Office 365 is a potential security problem. We have MFA turned on, but if users stay signed in another person may access the tenant if the computer is left unattended or is hacked. It was possible to turn this option off in Company Branding in AAD until the latest (preview) version of Company Branding was released. For some reason that feature is not available in the latest version. I assume I can revert to the previous version, and then turn it off, but when doing that, I receive a warning that it may have negative consequences for SharePoint Online, but it doesn't say what those consequences are. So, my questions are: 1. Can I turn it off by reverting to the previous version of Company Branding and what are the consequences? 2. Is it possible to achieve the same result in another way? PowerShell or Conditional Access maybe?42KViews1like4CommentsWindows AD account password expired but user can still send/receive email and use Teams
Hi. I recently discovered that some users with expired AD passwords are still working as if nothing has changed, which caught me by surprise. All the users affected do not use the VPN on a regular basis, or sign into Office 365. They all use desktop office for their email (Outlook) and chats (Teams). We are all still working from home. It appears as if a user is only challenged to update their expired password once they physically authenticate against the domain controller(s). But what if they never do? This means a user with an expired password will continue to send/receive emails and send chats in Teams regardless of when their password expired, unless they perform some form of "logon". I ran a PowerShell script to elucidate more and found that we have dozens of users in this boat. Some users have passwords that expired YEARS ago! Is this by design? In that the password expiration attribute is pointless until said account actively connects or authenticates to the domain? Why is the "expiration" attribute not part of the user SID? I'm baffled. We have on premise domain controllers which syncs out to Office 365 via ADSync and this is syncing fine with no errors, including password sync. Any help appreciated.Solved32KViews0likes2CommentsAzure AD SSPR Password write back issue
Hi all, A company I work for have issues with the reset password function with AD Connect. In the SSPR audit logs in Azure AD, we face on 'Reset password (self-service)' the status reason 'OnPremisesAdminActionRequired', with a follow up event log within the AD connect server: event ID: 33004 with error "hr=80230626, message=The password could not be updated because the management agent credentials were denied access" I face this issue before and this was causing because the AD DS connector account did not have the right permissions. In this case this is not. What I have done so far: - Updated AD Connect from 2.0.89.0 to 2.0.91.0 - enforced TLS 1.2: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fhybrid%2Freference-connect-tls-enforcement&data=04%7C01%7CRicardo.van.der.Linden%40wortell.nl%7C99649d63055b44e871c308d9ec7ff08b%7Cb1a6616c94734cab82b6b6affeed3e12%7C1%7C0%7C637800856524039043%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=GRdHd0Swz7JMK45OAg4Z0MmOC2TwvwT6iu%2BlSbiIC%2BY%3D&reserved=0 - Checked AD DS connecter account 'MSOL_xxxxxxxx' permissions: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fauthentication%2Ftroubleshoot-sspr-writeback%23verify-that-azure-ad-connect-has-the-required-permissions&data=04%7C01%7CRicardo.van.der.Linden%40wortell.nl%7C99649d63055b44e871c308d9ec7ff08b%7Cb1a6616c94734cab82b6b6affeed3e12%7C1%7C0%7C637800856524195272%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=eUD%2Fdx9FTc0VvcjXxvGksfS30ZD9SKsbl9LQK1d1eA0%3D&reserved=0 - the user do not have the options 'password never expires' or 'user cannot change password' configured - Let AD connect talk to another DC dc02 instead of dc01 - Checked connection to SSPR service from DC's : Test-NetConnection -ComputerName ssprdedicatedsbprodscu.servicebus.windows.net -Port 443 - The action 'Change password (self-service)' are successful (via my account portal) , only action 'Reset password (self-service)' face this issue (via passwordreset.microsoftonline.com) -- both use the same OnPremisesAgent ->> AADConnect Have anyone a idea what else I can try more? Regards, RicardoSolved25KViews0likes13CommentsOffice 365 MFA using code sent to email, instead of getting request on Microsoft Authenticator
I am working on a tenant which have 400++ sites, and we need to force this permission settings for external user sharing:- Set the share permissions on all sites to allow for only external users if they are invited by email and requires MFA for a code sent to their email to authenticate So is this something we can achieve, to force the MFA code to be sent to email rather than mobile phone? Second question, If the answer to the above question is Yes, then will this need to be done on the site level or on the tenant level? If this need to be set on each site separately, then can we do this using Power shell, where we can loop through all the sites inside the Power-shell, but how we can set this setting using Power shell?Solved18KViews0likes1CommentWindows Hello for Business 0x80090010 NTE_PERM
Hi all, I'm encountering an issue with Windows Hello for Business on the latest version of Windows (July 2025 update). The setup process fails during initialisation, and no biometric or PIN options are being provisioned for the user. Environment: Windows version: 11 24H2 Enterprise (latest update) Deployment mode: Hybrid Cloud Trust Hybrid joined devices Symptoms: Users are prompted to set up WHfB but the process fails at the last step with error 0x80090010 Users who already have WHfB authentication methods created can successfully login Event ID 311 & 303 in the User Device Registration logs Screenshots: Troubleshooting so far: Unjoined and rejoined to Entra ID Granted modify permissions on folder in which NGC container would be created Rolled back to June 2025 update (this worked) So it seems like this is caused or related to the latest Windows Update, which is rather unfortunate for us as we are just beginning to rollout WHfB for our organisation. I'm posting here to raise awareness of the issue, if there is a more appropriate place to post then please suggest.14KViews6likes17CommentsMulti-factor Authentication (MFA) via Security Defaults enforced on tenants by Microsoft (status)
Hi all, - Security Defaults is enabled by default on all newly created Microsoft 365 tenants. - Microsoft has started enforcing Multi-factor Authentication (MFA) on all tenants. - MFA will not be enforced on tenants using Conditional Access policies (at least one Azure AD Premium P1 license is required to be able to use Conditional Access policies). - Self-service password reset (SSPR) will enforce Multi-factor Authentication on all accounts (and the breakglass account) but SSPR can be disabled. - Please check admin.microsoft.com >Health > Message center regarding notification. - Security Defaults requires all users to register for MFA within 14 days; however, users can postpone this registration. After 14 days, they will be forced to do the registration; however, this happens during interactive sign-ins. - If a user doesn't perform the MFA registration and a bad actor figures out the user's password, they can register their phone or authentication app as an MFA method. It is recommended: - to use MFA company-wide because this security-feature prevents 99.9% of attacks on your accounts. - to revoke existing tokens to require all users to register for multifactor authentication. This revocation event forces previously authenticated users to authenticate and register for multifactor authentication. https://learn.microsoft.com/en-us/microsoft-365/business-premium/m365bp-turn-on-mfa https://learn.microsoft.com/en-us/microsoft-365/admin/add-users/let-users-reset-passwords https://learn.microsoft.com/en-us/entra/fundamentals/security-defaults#revoking-active-tokens11KViews0likes1CommentAdd filters/ grouping to microsoft authenticator app accounts
Hello! Hope you are all well! I would like to see filters of personal/ Work and school accounts or by domain. Or even the ability to organise accounts manually into groups. Currently have a long list of personal accounts and work account.8.6KViews8likes10CommentsHow to change Directory sync service account in AAD connect ?
Since the Global admin account and the Service account is same, we are not able to apply MFA on it. Hence want to change the Sync service account. We tried to reconfigure the setting but dirsync service account is same i.e Global admin7.1KViews0likes1CommentPassword-less authentication with using One-time passcode from Microsoft Authenticator App.
Recently one of my users was in Internet restricted zone and when he tried to sign-in with Password less method, He didn't get the code due to no internet in mobile and in addition to this, he forgot the user sign-in password. Is there any method or way to setup that we can be able to sign-in with using the 6-digit Microsoft Authenticator App Code instead of the push notification and password.6.4KViews0likes2CommentsAllow any UTF8 characters in Microsoft account passwords
Hello, I tried to use characters like «¼∃≒∀» in passwords and the form always reject them while local windows accounts and on premise domain controllers accept them. I opened a support ticket to report this as a bug and was told it works this way by design (case 28980531). Was also directed here if I had any suggestions so here I am: please allow any and each UTF8 characters in your online service in the password field. Not being able to is a regression from using on premise domain controller that gladly accept even emojis in passwords. Thank you.4.9KViews0likes3Comments