When creating a policy for a sensitivity label you have the option to set a default label for the user the policy is pointed at. You can get more information on this process at the “Apply a default label” item on Microsoft’s Learn About Sensitivity Labels page. This method, however, has a limitation. It only works within a mail client that can connect to the Microsoft 365 Security/Compliance endpoints. Doesn’t seem like a huge issue right? Well, what about automated notifications that are sent via Power Automate or another custom solution that doesn’t utilize the Outlook (or other) client? I’ve tested this. It doesn’t work. If I send it from Outlook or OWA I get the default label. If I have an automated process within Power Automate it doesn’t. In this post, I will show you how you can apply sensitivity labels for automated processes so all of your emails can contain a sensitivity label.
When dealing with sensitive information within Microsoft 365 you often need to utilize a sensitive info type. This is an entity within the security console that groups data by the sensitive information it contains. For example, a credit card is a sensitive info type and is configured to look within content for credit card number formats. Luckily, Microsoft provides 100 pre-configured sensitivity types and they really cover a large number of possibilities. Well, what if you have a type of sensitive data that isn’t in the provided templates. Well, that’s where this blog post comes in handy. In this post, I will show you how to create a sensitive info type in Microsoft 365’s security console.