Forum Discussion
Microsoft 365 F1 license having problem in setting up
We are rolling out F1 license https://www.microsoft.com/en-us/microsoft-365/enterprise/f1 I know that with F1 license we don't get mailbox, but we found that we are able to send email to these user...
I'd avoid calling anything related to F1 "best practice", it's a stupid decision MS made on this. I mean the service description literally tells you to ask the users to not login to the mailbox, genius! 🙂
Anyway, if you want to avoid getting NDRs, you can create a mail flow rule to silently drop any messages addressed to said mailbox(es). There's a sample rule here, simply adjust the conditions: https://docs.microsoft.com/en-us/exchange/security-and-compliance/mail-flow-rules/use-rules-to-block-executable-attachments#use-the-eac-to-create-a-rule-that-blocks-messages-with-executable-attachments
Anyway, if you want to avoid getting NDRs, you can create a mail flow rule to silently drop any messages addressed to said mailbox(es). There's a sample rule here, simply adjust the conditions: https://docs.microsoft.com/en-us/exchange/security-and-compliance/mail-flow-rules/use-rules-to-block-executable-attachments#use-the-eac-to-create-a-rule-that-blocks-messages-with-executable-attachments
hey thanks for the reply. i am not an expert here in exchange, but what i understand is that when user A sends an email (e3 license or having a mail box) to user b (f1 license no mailbox) , how can i identify this use case and customise the msg that this is not supported?
this can be done by creating a rule in exchange online?
this can be done by creating a rule in exchange online?
- Hi,
We are faced with the same issue. Have you been able to find a "good enough" solution? - Take a look at the article above and the references therein. Exchange offers a robust mail flow rule engine which allows you to "capture" such messages, redirect them, or prevent delivering them altogether.
