authentication
778 TopicsMicrosoft Authenticator Backup Restored but All Third-Party Accounts Missing
Hello Microsoft Community, I am facing a serious issue with Microsoft Authenticator after factory resetting my Android phone. My situation: I was using Microsoft Authenticator on my Android phone before the factory reset. Cloud Backup was enabled before the factory reset. I used the same Microsoft personal account for backup and recovery. After factory resetting my phone, I reinstalled Microsoft Authenticator. I successfully signed in using the same Microsoft account. The app showed that cloud backup recovery was successful. However, all my previously registered third-party authentication accounts are missing. Important: The recovery process completes successfully, but none of my previous authentication accounts or OTP codes have returned. Affected accounts include: Google account Namecheap account Other third-party services previously registered in Microsoft Authenticator. What I have already tried: Reinstalled Microsoft Authenticator. Restored using the same Microsoft account. Checked that the app is updated. Verified that OneDrive files are accessible. Contacted Microsoft Support through live chat. Microsoft Support informed me that they cannot directly access, inspect, or restore individual Authenticator backup contents. My questions: Why does Microsoft Authenticator report successful cloud backup recovery while all third-party accounts are missing? Is there any possibility that my previous authentication data still exists in Microsoft's backup infrastructure? Is this a known issue with Microsoft Authenticator on Android? Is there any advanced recovery procedure, diagnostic method, or workaround? Can a Microsoft Authenticator product specialist or engineering team investigate this issue? Is there any possibility of recovering my previous TOTP authentication accounts? I understand that Microsoft Support may have limitations regarding encrypted backup contents. However, I would appreciate technical guidance from experienced Microsoft Authenticator specialists or community members. I am willing to provide my Android version, app version, and other technical details if required. Thank you for your time and assistance.69Views0likes3CommentsLocked out of M365 Admin (Error 500121) – Direct web purchase, sole admin MFA reset
Hello Microsoft Support Team and Community, I am currently locked out of my Microsoft 365 Business Admin account and need assistance escalating my case to the Data Protection Team for an MFA reset. Here are the details of my situation: Error Code: 500121 (Authentication failed / MFA loop) Admin Role: I am the sole Global Administrator for this tenant. Purchase Channel: I purchased the subscription directly from the Microsoft website (not through a CSP/vendor), so I do not have a partner who can reset my MFA. Issue: My Microsoft Authenticator app on my device is out of sync and does not generate any verification codes or push notifications, and I do not have backup verification codes saved. Because I cannot sign in to the Admin Center, I am unable to submit a support ticket through the portal. Could a Microsoft Moderator please assist me or initiate a Private Message so I can provide my tenant domain and contact details to verify ownership and get connected with the Data Protection Team? Thank you in advance for your help.71Views0likes1CommentBrowser keeps showing a second work account in Microsoft's "Pick an account" screen
Hi all, Hoping someone has run into this before. WHAT I'M TRYING TO ACHIEVE I have two work accounts in the same Entra ID tenant: my standard account (the device's primary user) and a separate privileged (P) admin account. I want a clean split: - Edge: privileged account only - Chrome: standard account only In Chrome, I'd like Microsoft 365 apps to sign me straight in with my standard account, without the "Pick an account" prompt showing the P account every time I open an app. SETUP - MacBook on macOS [version], enrolled in Intune via Company Portal - Chrome [version], Edge [version] - Microsoft Single Sign On extension 1.0.11 in Chrome, installed by policy (the toggle is greyed out, so I can't disable it) EDGE (SOLVED) - Created a new Edge profile for the P account and deleted the old profiles - Turned off "Automatic sign in on Edge" and the two single sign-on toggles under Profile preferences - Hit a Conditional Access enrollment error for the P account for a while, which eventually cleared up (not sure exactly what fixed it) - Re-registered a Touch ID passkey for the P account, since the old one lived in a deleted profile Edge now works exactly how I want. CHROME (STILL UNRESOLVED) The "Pick an account" screen still lists the P account as "Signed in". So far I've tried: - Signing out of the P account from the picker, then choosing "Forget" - Signing it out from the Microsoft 365 account menu - Clearing all cookies and site data (All time), including microsoftonline.com, microsoft.com, office.com and live.com - Deleting the P account's passkey from Chrome's passkey manager (the passkey is gone, the account isn't) - Fully quitting and reopening Chrome after each step In an Incognito window, where the extension isn't enabled, no accounts appear at all. Because the P account survives a full cookie wipe, my guess is the SSO extension is pulling it from the macOS SSO broker (Company Portal / Enterprise SSO), since I've signed in with it in Edge. MY QUESTIONS 1. Is there a way to remove or hide one specific account from what the SSO extension exposes to Chrome, without breaking device compliance or the P account in Edge? 2. Is there an admin-side setting (Intune or Chrome policy) to limit the extension to the device's primary user only? 3. If neither is possible, is there a recommended way to use a privileged account alongside a standard one on a managed Mac? Any pointers appreciated. Thanks!162Views0likes5CommentsCannot Authenticate sign in
I have a Microsoft 365 business account with 2 users. Today my wife opened Outlook on her laptop and it asked for her password. She entered it and was directed to the Microsoft authenticator app, to verify. She opened the app and it asked her to sign in, she did and was asked for an authenticator code to verify. She couldn't do this as she was trying to sign into the app. It offered two ways to verify, both of which requires her to sign into the authenticator app! I went into the admin consol to remove authenticator, to find it's not setup? How can I get around this, in the consol i setup her mobile as an authentication method but the microsoft authenticator app doesn't show text as an option. How do i get around this?Solved151Views0likes6CommentsCannot Authenticate sign in
I have a Microsoft 365 business account with 2 users. Today my wife opened Outlook on her laptop and it asked for her password. She entered it and was directed to the Microsoft authenticator app, to verify. She opened the app and it asked her to sign in, she did and was asked for an authenticator code to verify. She couldn't do this as she was trying to sign into the app. It offered two ways to verify, both of which requires her to sign into the authenticator app! I went into the admin consol to remove authenticator, to find it's not setup? How can I get around this, in the consol i setup her mobile as an authentication method but the microsoft authenticator app doesn't show text as an option. How do i get around this?104Views0likes2CommentsMicrosoft Entra ID Provisioning: SelectUniqueValue and the "Apply this mapping" limitation
In Microsoft Entra ID's provisioning service, the SelectUniqueValue() expression has a specific restriction: When an attribute mapping uses SelectUniqueValue(), the "Apply this mapping" setting must be configured as "Only during object creation." It cannot be configured as "Always." This restriction is related to how the provisioning engine generates unique attribute values and how those values are maintained throughout an object's lifecycle. 1. How SelectUniqueValue() works The SelectUniqueValue() function evaluates a list of candidate values in priority order and selects the first value that does not conflict with an existing value in the target directory. For example, consider generating a user's userPrincipalName: SelectUniqueValue( Join("", [FirstName], [LastName], "@company.com"), Join("", [FirstName], ".", [LastName], "@company.com"), Join("", [FirstName], [LastName], [EmployeeID], "@company.com") ) The provisioning engine evaluates candidates in sequence: JohnSmith _AT_ company.com John.Smith _AT_ company.com JohnSmith12345 _AT_ company.com It selects the first available candidate. The important distinction is that this is a uniqueness-selection operation, not simply a string transformation. 2. Why the "Always" setting is incompatible Consider the following scenario. Initial provisioning Two employees exist: Employee Generated UPN John Smith (Employee 100) JohnSmith _AT_ company.com John Smith (Employee 200) John.Smith _AT_ company.com The second employee receives the alternate UPN because the preferred value is already taken. Subsequent provisioning cycles Suppose Employee 100 leaves the organization and email address removed for privacy reasons eventually becomes available. If SelectUniqueValue() were evaluated continuously as an ordinary update mapping, Employee 200 could potentially receive a different result: Attribute Value Existing UPN John.Smith _AT_ company.com Newly preferred candidate JohnSmith _AT_ company.com That could result in an unwanted identity change, even though Employee 200's name and other source attributes have not changed. Restricting the mapping to object creation avoids this class of problem. There is also an important implementation distinction: selecting a unique value during creation is different from evaluating whether an existing object's current value should be retained during an update. The latter requires preserving identity stability, not merely finding an available candidate. The example illustrates the design rationale; it does not establish that Microsoft's engine would actually perform that reassignment if the restriction were removed. 3. What Microsoft officially documents Microsoft explicitly states that: SelectUniqueValue() is intended only for object creation. The mapping must use Only during object creation. The function must be top-level and cannot be nested inside another function. The target attribute cannot have a matching precedence configured. These are documented product restrictions, not merely recommended practices. Microsoft Learn+1 Microsoft does not explain the internal implementation reason for the creation-only restriction in that documentation. The identity-stability explanation above is a plausible rationale, rather than a confirmed statement from Microsoft engineering. Official reference: https://learn.microsoft.com/en-us/entra/identity/app-provisioning/functions-for-customizing-application-data?utm_source=chatgpt.com#selectuniquevalue 4. Implications for Workday-to-Active Directory (or any external directory) provisioning This limitation becomes particularly relevant when provisioning sAMAccountName or userPrincipalName from Workday. Suppose an employee's last name changes: Event Desired UPN Initial hire Jane.Smith _AT_ company.com Marriage/name change Jane.Jones _AT_ company.com With SelectUniqueValue() configured for object creation, the provisioning service will not reevaluate the UPN mapping for the existing AD user. Consequently, you cannot use that same mapping to both: Generate a collision-free UPN when creating a user. Automatically update the UPN when Workday reports a name change. 5. Feature Request / Future Development: Removing the SelectUniqueValue() Restriction Microsoft could significantly improve the Entra ID provisioning service by extending SelectUniqueValue() to support the "Always" attribute mapping setting, allowing uniqueness validation during both object creation and subsequent updates. The current restriction creates a functional gap in identity lifecycle management, particularly for organizations integrating authoritative HR systems such as Workday with Active Directory. 5.1 Proposed enhancement Microsoft should introduce an update-aware implementation of SelectUniqueValue() that supports the following behaviors: Preserve existing values: If the target attribute already contains a valid value and the source attributes have not changed, retain that value rather than selecting a different candidate. Detect source attribute changes: When an authoritative source attribute changes, such as FirstName, LastName, or PreferredName, reevaluate the expression and determine whether an identity update is appropriate. Perform uniqueness validation: Evaluate candidate values against existing objects in the target directory, excluding the object currently being updated. Support collision-free updates: If the preferred candidate is already assigned to another object, evaluate subsequent candidates in the expression, just as the function does during initial provisioning. Maintain identity stability: Prevent unintended renaming simply because a previously unavailable candidate becomes available. 5.2 Proposed configuration options Rather than simply removing the restriction, Microsoft could introduce an additional configuration setting governing how uniqueness expressions behave during updates. Proposed mode Behavior Creation Only Current behavior; evaluate only during initial provisioning Always — Preserve Existing Retain the existing value unless it is empty or an explicit reevaluation condition is met Always — Reevaluate on Source Change Recalculate when relevant source attributes change Always — Force Reevaluate Recalculate on every provisioning cycle, even when source attributes remain unchanged The "Always — Reevaluate on Source Change" option would be particularly valuable for HR-driven identity provisioning. 5.3 Technical considerations for Microsoft To implement this functionality reliably, Microsoft would need to address several technical challenges. Self-exclusion during uniqueness checks When evaluating a candidate against Active Directory, the provisioning engine must exclude the current object's identity from the uniqueness search. Otherwise, the existing user could incorrectly be identified as a collision with themselves. Concurrency and race conditions Two provisioning operations could generate the same candidate simultaneously. Microsoft should ensure that uniqueness is revalidated immediately before committing an attribute change, with appropriate conflict handling. Distinguishing source changes from directory changes A newly available username should not automatically trigger a rename. The engine should distinguish between changes in authoritative source attributes and changes in the availability of candidate values. Safe updates to identity attributes Updates to userPrincipalName, sAMAccountName, and other identity-related attributes can affect authentication, email addressing, and downstream applications. The feature should provide optional controls for preserving existing values, auditing changes, and restricting automatic renaming. 5.4 Business justification This enhancement would deliver several benefits: Complete identity lifecycle automation: Support initial provisioning and subsequent identity changes using the same expression framework. Reduced administrative overhead: Eliminate the need for custom PowerShell scripts, scheduled tasks, or external automation solely to manage uniqueness during updates. Consistent naming policies: Apply the same collision-handling rules throughout an employee's lifecycle. Improved reliability: Reduce the risk of duplicate identities and inconsistent naming conventions. Better HR integration: Allow Workday and other authoritative HR systems to drive name changes without requiring separate provisioning mechanisms. 5.5 Recommended feature request to Microsoft Feature Request: Support SelectUniqueValue() with "Always" Attribute Mapping in Microsoft Entra ID Provisioning Product: Microsoft Entra ID — Inbound HR Provisioning / Workday to Active Directory Current Limitation: The SelectUniqueValue() expression is restricted to attribute mappings configured with "Apply this mapping" set to "Only during object creation." This prevents organizations from using the provisioning service's built-in uniqueness validation when updating existing Active Directory objects. Requested Enhancement: Extend SelectUniqueValue() to support the "Always" mapping option, enabling uniqueness validation during both object creation and updates. The enhanced functionality should: Exclude the current target object from uniqueness checks. Support reevaluation when relevant source attributes change. Preserve existing values when no relevant changes have occurred. Evaluate alternate candidates when a proposed value conflicts with another directory object. Provide configurable controls to prevent unintended identity changes. Business Impact: Organizations using Workday or other HR systems as authoritative identity sources cannot fully automate changes to identity attributes such as userPrincipalName and sAMAccountName while maintaining uniqueness through the native provisioning expression engine. This limitation requires additional automation outside Microsoft Entra ID, increasing operational complexity, maintenance requirements, and potential points of failure. Expected Outcome: Enable Microsoft Entra ID provisioning to provide consistent, collision-aware identity attribute management throughout the complete employee lifecycle, including initial hiring, name changes, rehiring, and other HR-driven identity updates. This enhancement would reduce dependence on external scripts and improve the completeness of Microsoft's native HR-driven identity provisioning capabilities. 5.6 Current Microsoft position Microsoft's documentation continues to explicitly restrict SelectUniqueValue() to object creation. I found no documented commitment or announced release date for update support. Microsoft Learn+1 The feature request above is therefore a proposed product enhancement, not an existing capability or announced roadmap item.137Views0likes2CommentsGetting account back after hack
I have lost my account to a hacker, and whenever i try to do the account recovery form i get a response the same minute that they dont think its me, i still have the gmail thats connected to the account but cant use that to prove that i am the owner, since the recovery mail has been moved How can i prove that the email the account is registered under wants to change the password? Im only writing here since i am running out of options99Views0likes3CommentsWhen Authorization Changes Before Execution, Who Is Responsible for Validating Authority?
When Authorization Changes Before Execution, Who Is Responsible for Validating Authority? I've been exploring an architectural security question at the intersection of Microsoft Entra Workload Identity, Conditional Access, and Zero Trust. The question is: Can an identity remain successfully authenticated and authorized while the authority to perform a specific action becomes invalid because the execution context has changed? Consider a practical scenario: A workload identity is successfully authenticated. Authorization is granted for a particular operation. Before the operation executes, the surrounding conditions change. The application proceeds toward execution using previously established authorization. At that point, who is responsible for validating that the action is still authorized under the current execution context? Is that responsibility primarily held by: Identity layer: Establishing and maintaining the identity and its credentials? Policy enforcement layer: Evaluating changing conditions and authorization policies? Application layer: Validating authority immediately before executing an operation? Shared responsibility: Coordinating enforcement across all three layers? I'm not suggesting that Microsoft Entra currently fails to address this scenario, nor am I assuming that one layer should own the entire problem. I'm interested in understanding how the Microsoft community approaches the architectural boundary between: Workload identity lifecycle Delegated authorization Continuous evaluation of context Runtime policy enforcement Execution-time action validation This question becomes particularly interesting as organizations introduce autonomous AI agents and increasingly delegate operations to workloads that can act across multiple services. My question to the community: After authentication succeeds and authorization is granted, where should responsibility for validating continued authority reside when the execution context changes before an action occurs? Is this fundamentally an identity problem, a policy-enforcement problem, an application responsibility, or a combination of all three? I'd particularly welcome perspectives from Microsoft Entra engineers, identity architects, Conditional Access practitioners, and developers working with workload identities and AI agents. I'm interested in both practical implementation experiences and broader architectural principles. Thanks for sharing your perspectives. Kris Park Master Combine | Sovereign Engine Assurance Group214Views1like2CommentsHacked Microsoft Account Recovery with Semi Access
I'm at a complete loss and it is infuriatingly ridiculous. I am entirely unable to get a hold of a human being at Microsoft and am being turned down by automated responses nonstop. So here's what's happening: My Microsoft account has been hijacked (obviously not this one) for its valuable Minecraft account and has now been sold. I am logged into my account via my PC, have full access of the main email address, but I have been locked out of my account using the alias email. Whenever I want to log in to my account, it wants to instead send a code to an email address I do not own and can't access. I have tried the Sign-In Helper, the Recovery Form, the hotline, the support email without any result, let alone a non-automated response. I sadly don't have the Recovery Code of my 15 year old-ish account. Since I still have full access of my email address I get updates of security info being changed and what not. Last month a stranger sent me screenshots of someone trying to sell my Minecraft account, for which I myself have received multiple buying offers, and voila yesterday I received notification of my alias mail address changing followed by Minecraft server apps being added to my Microsoft account. While I had already given up retrieving my account, whenever I get notifications my heart sinks a new while some hope sparks up again. Do you people have any idea of what I could do? I don't even rule out legal actions at this point. While I do of course have the email address of the hijacker and the buyer, I fear that contacting them results in me being locked out permanently. I'm just begging to catch the attention of anyone involved with Microsoft. This being walled out with automated responses is killing me.310Views1like3CommentsNo acces to local Office365 apps with an account which differs from the current windows account
Hi, guys! I'm working with Windows 11 Pro using the Microsoft account ABC. Today I bought a Office 365 Family License - by using another Microsoft account XYZ. I downloaded the local apps successfully... ...but when I start the local app and tried to sign in using the XYZ account, I'm asked for the Windows Hello Pin for the XYZ account - but there is no PIN for that, because the account doesn't exist as a Windows account at this computer at all. Copilot says: "You can sign in to Windows 11 with one Microsoft account and use a different Microsoft 365/Office account for Office applications. Microsoft supports this setup." What did I wrong - what can I do? Kind regards! Sebastian232Views0likes2Comments