While writing a couple of posts recently I became a bit out of step with my intended schedule by discussing sensitivity for automated processes before actually discussing how Microsoft 365 deals with sensitive content. This is fine if you are familiar with information protection within Microsoft 365, but for those of you who are not let me get back on track and discuss information protection concepts within Microsoft 365. This is the overview first in a series of posts that I will explain and demonstrate how Microsoft 365 protects an organization’s sensitive information.
In a couple of previous posts, I covered retention labels and how to apply them within your tenant. An option when creating retention labels is to have your document declared a record when the policy/label is applied. Records add an extra level of content security to your documents. Now keep in mind I don’t mean information security in this case. Declaring a document won’t keep your information from entering the wrong hands or being used improperly. We’ll cover those topics in the future. A record instead protects the content within the document. Read on as I explain Office 365 records management.
So today I started creating a new custom approval using Microsoft Flow. I had been working for about 15 minutes or so and thought to myself that it may be a really good idea for me to save my work because we all know that if I didn’t do it soon something would cause me to lose everything (because initial save hadn’t been accomplished yet. When I clicked on the save button I received an error I hadn’t received before. “Tag value to large. Following tag value…exceeded the maximum length. Maximum allowed length for tag value – ‘256’ characters.