Fehlermeldung - This sender failed our fraud detection checks and may not be who they...

Hallo Thomas,

Wurde deine Frage damit beantwortet? Benötigst du weitere Hilfe?



Freue mich auf deine Rückmeldung.

Mit freundlichen Grüßen,

Georgi Taskov

Microsoft Office 365 Support Engineer

Hallo Thomas,



Bitte schaue dir erstmal die Information, die in den Link in der Meldung steht - "Schutz
vor Phishingversuchen und anderen Formen von Onlinebetrug".



Wird die Meldung für einen bestimmten Absender angezeigt?



Kennst du diesen und ist der Inhalt der E-Mails wirklich kein Phishing oder eine andere Form von Onlinebetrug, SMAP, etc. ?



Werden irgendwelche Anhänge versendet? Falls ja, bitte erstmal diese nicht öffnen, bis nicht sichergestellt ist, dass letztere nicht gefährlich sind. Im Zweifelsfall kannst du den Absender kontaktieren und ihn darüber erfragen.



Falls das wirklich keine gefährliche E-Mails sind, kannst du die E-Mail-Adresse oder die Domäne des Absenders als sichere Adresse / Domäne hinzufügen.



Für lokal in Outlook siehe - "Hinzufügen
von E-Mail-Empfängern zur Liste sicherer Absender".



Outlook -
Junk-E-Mail-Filter (Übersicht).



Auf Office 365 Organisationsebene (wird vom Office 365 Administrator eingerichtet):



Konfigurieren der Verbindungsfilterrichtlinie.



Verhindern,
dass E-Mails in EOP und Office 365 als Spam gekennzeichnet werden.



Office 365-Antispamschutz für E-Mails.



Blockieren
von Spam-E-Mails mit dem Office 365-Spamfilter, um Probleme mit falsch negativen Ergebnissen zu vermeiden.





Freue mich auf deine Rückmeldung.

Mit freundlichen Grüßen,

Georgi Taskov

Microsoft Office 365 Support Engineer

Hello Anonym_18

Hi, I'm Karl and will be happy to help you today.

Unfortunately there is no option to filter who can try to log into the account. That option simply does not exist.

You may want to consider enabling 2 factor authentication if it is not already.

Hello Mas

I'm Diane, a Microsoft 365 Apps & Services MVP.and I'll try to help you today.

No, they will not be changing the naming convention in the foreseeable future. If they ever change the account name requirements (which is unlikely), the existing accounts will continue to work.

-- Diane

Give back to the Community. Help the next person who has this issue by indicating if this reply solved your problem. Click Yes or No below.

<br />

Im Admin Panel steht untenstehendes.

Tatsächlich hat bei mir geholfen: Outlook schließen. Word öffnen. Dort abmelden. Word schließen. Outlook öffnen.

Title: Outlook client connectivity issues in specific scenarios

User Impact: Users with multiple enterprise sign-in accounts can't connect to Exchange Online via the Outlook desktop client. More info: Further investigation shows that this issue is specific to users with
multiple related and trusted Enterprise log-in accounts across Microsoft 365 and Windows. If you have users experiencing issues connecting to the service or impact outside of what is described, please submit a ticket with support. Users experiencing this problem
will see the Outlook desktop client showing as disconnected and may receive the following error when attempting to send mail: "Sending and receiving reported error (0x80040115). The connection to the Microsoft Exchange Server is unavailable. Outlook must be
online or connected to complete this action." Users may be able to leverage one of the following options to circumvent impact for this event: - Affected users may be able to use Outlook on the web or mobile clients to access their mailboxes. - Additionally,
users may be able to restore access by forcing new authentication to all office apps as noted below: 1) Close Outlook and other Office applications. 2) Open an Office desktop application, such as Word, PowerPoint or Excel. 3) Navigate to File > Account > Switch
accounts, and then click the ellipsis next to the account that's not having the problem. 4) Click Sign out and then OK. *Note: Users that have multiple accounts may find it difficult to determine which account to sign out of; though, they should be able to
sign back in later if there is an issue with this process. 5) Close the Office application used for this process and re-start the Outlook desktop client. 6) When prompted for a password, click "sign in to a different account" and enter the correct information.
- Lastly, affected users may be able to restore access by creating a new Outlook profile, further instructions can be found via the following link. https://support.office.com/en-us/article/overview-of-outlook-e-mail-profiles-9073a8ac-c3d6-421d-b5b9-fcedff7642fc
Although we acknowledge that these workarounds may not be viable for all users, we're committed to providing potential solutions to improve the end-user experience. If you would like to provide feedback on these workarounds, using a non-mobile device, please
rate this post and submit it in the text box. Current status: We’ve finished installing and enabling the focused telemetry. The data gathered from this telemetry will help identify instances of service errors specific to the Outlook desktop client, which will
be analyzed to determine if any recent client-specific changes led to this event. Concurrently, we’re implementing a set of reproduction experiments in our test environment to better isolate the specific criteria causing the incorrect user authentication token
to be delivered when connecting to Exchange Online via the Outlook desktop client. Scope of impact: Users may experience this issue if they operate multiple related and trusted Enterprise log-in accounts across Microsoft 365 and Windows. Root cause: A desktop
client-specific issue that occurs for users with multiple accounts is causing the incorrect authentication token from those accounts to be delivered to our systems when connecting to the Exchange Online service.
Next update by: Friday, August 2, 2019, at 7:00 PM UTC