How to allow auto-forwarding to Teams channels

Email forwarding can be useful, but poses a security risk due to the potential disclosure of information. Therefore the Anti-spam outbound policy blocks the auto-forwarding at the tenant level by default. Although this minimises the security risks, it hampers productivity since there are valid reasons to allow auto-forwarding to an external domain.

There are valid use cases for external email forwarding such as:

  • To support the adoption of Microsoft Teams and the concept of working in Teams rather than sending email. However, users cannot auto-forward emails to a Teams channel, because the Teams channel email addresses are external email addresses, for example ( or
  • Auto-forwarding emails to a third-party system, such as CRM or ticketing system for processing.

Read on to learn how to allow auto-forwarding to Teams channels and other authorised external domains to increase productivity and reduce security risks.

Read More

How to use sensitivity labels to control access to Microsoft Teams, Groups and Sites

Are you using Microsoft Purview sensitivity labels to control access to Microsoft Teams, Groups and Sites? If not, why not?

Did you know that your Guest access and external sharing controls are managed at the tenant level? As a result, security becomes ‘one size fits all’ rather than providing granular security controls based on Teams, Groups, and Sites’ confidentiality requirements.

For example

  • When guest access is enabled, Team owners can add external guests to all Microsoft Teams, Groups and SharePoint sites.
  • When you create a new Team or a Group, the default SharePoint external sharing is set to New and existing guests unless your tenant setting is more restrictive. So Team members can share Team content externally.

Check out the information below to learn how you can use sensitivity labels to apply granular security controls to Teams, Groups, and Sites.

Read More