Windows 10: I had an attempted hacking into my Microsoft Authenticator from Russia & I tried to disable...

**I had an attempted hacking into my Microsoft Authenticator earlier this year from Russia, and I tried to disable the whole thing at that time. Now I want to try to set it up again, but the entire process is much too complicated even though I am somewhat knowledgeable with computers. Is there a way to get detailed simple instructions beginning from square one? I am a home user and have no expert to assist me. AADSTS90072: User account '*** Email address is removed for privacy ***' from identity provider 'live.com' does not exist in tenant 'Microsoft Services' and cannot access the application '0000000c-0000-0000

:)

 

I had an attempted hacking into my Microsoft Authenticator (from Russia) & I tried to disable this app. Now trying to set up again. Help!

**I had an attempted hacking into my Microsoft Authenticator earlier this year (from Russia), and I tried to disable the whole thing at that time. Now I want to try to set it up again, but the entire process is much too complicated even though I am somewhat knowledgeable with computers. Is there a way to get detailed simple instructions beginning from square one? I am a home user and have no expert to assist me.

*** Email address is removed for privacy ***

Troubleshooting details

If you contact your administrator, send this info to them.

Copy info to clipboard

Request Id: b44dd4c3-0b65-4556-85b1-6180d8a5b201

Correlation Id: 6de1c08b-c03b-4599-9369-cdb1051f0bd9

Timestamp: 2023-12-26T22:12:36Z

Message: AADSTS90072: User account '*** Email address is removed for privacy ***' from identity provider 'live.com' does not exist in tenant 'Microsoft Services' and cannot access the application '0000000c-0000-0000-c000-000000000000'(Microsoft App Access Panel) in that tenant. The account needs to be added as an external user in the tenant first. Sign out and sign in again with a different Azure Active Directory user account

Flag sign-in errors for review: Enable flagging

If you plan on getting help for this problem, enable flagging and try to reproduce the error within 20 minutes. Flagged events make diagnostics available and are raised to admin attention.

 

Windows Microsoft account authentication

I have a valid Microsoft account and a Windows 10 PC with Hello/PIN account login enabled. I also have the Microsoft Authenticator app installed on an iPhone and configured for the Microsoft account. Additionally, I have two step authentication configured
for the Microsoft account. With all of that said, I have become very exasperated while trying to unravel the various authentication paths (and their security implications) through this multi level login security scheme. I find the associated account security
documentation to be woefully inadequate. Thus, I would like to pose the following list of questions for starters.

1. Does Windows Hello/PIN amount to a two step verification login procedure for my Microsoft account?

2. Does approving a Microsoft Authenticator login attempt (without two step verification explicitly set up)

amount to a two step verification login procedure for my Microsoft account?

3. Does approving a Microsoft Authenticator login attempt (with two step verification explicitly set up)

amount to a two step verification login procedure for my Microsoft account?

4. If answers to both 2 and 3 are yes, then what does explicit set up of two step authentication do?

5. Does a coherent, comprehensive document explaining Microsoft account security configuration exist somewhere?

6. If the answer to 5 is yes, wherer is it?

Thanks in advance.

 

Account syncronization problem after Microsoft Authenticator

Hi,

To better assist you with your concern, we'd like to ask for the following:

• Did you encounter an error message/code when syncing your mail to any devices?
• Have you tried to disable the Microsoft Authenticator to check if it is the one causing the issue?
• What specific troubleshooting steps have you done so far?

We look forward to your response.