locked
Mandating Labels with Customer Documents RRS feed

  • Question

  • We'd like to mandate labels for documents in our organization. But we also receive documents from our customers. Since our customers own these documents, it's not our say to apply a label. Therefore, customer-owned documents shouldn't be forced to have a label.

    What guidance can you provide in this scenario?

    We'd like to enforce labeling of our company documents but at the same time not label documents owned by the customer.

    Thanks for your time!

    Friday, June 22, 2018 12:22 PM

Answers

  • What's the downside of labeling these documents so that you (and end users) can easily identify them as documents owned by another company? For example, a label named "Confidential \ Customer".  For this label, don't configure visual markers such as headers, footers, or protection.  All you are doing is adding a custom property to the document.  If another company has Azure Information Protection, they won't see this label in their Office apps. 

    When you have labeled these documents, the metadata written to the document can be read by your internal systems so that they can tell the difference between these documents and documents that you do own but not yet labeled. In the future, you might have a need to identify documents that are owned by customers and passing through your infrastructure, and you can use your label to do this.

    Saturday, July 7, 2018 8:42 PM

All replies

  • What's the downside of labeling these documents so that you (and end users) can easily identify them as documents owned by another company? For example, a label named "Confidential \ Customer".  For this label, don't configure visual markers such as headers, footers, or protection.  All you are doing is adding a custom property to the document.  If another company has Azure Information Protection, they won't see this label in their Office apps. 

    When you have labeled these documents, the metadata written to the document can be read by your internal systems so that they can tell the difference between these documents and documents that you do own but not yet labeled. In the future, you might have a need to identify documents that are owned by customers and passing through your infrastructure, and you can use your label to do this.

    Saturday, July 7, 2018 8:42 PM
  • Makes sense, Carol.

    Thank you for taking the time to get back to me on this.

    Wednesday, July 11, 2018 8:40 PM