Microsoft Word Metadata Mac
When sharing Word documents, you may wish to remove document metadata, which is hidden or personal data. To remove document metadata follow these four steps. This feature works the same in all modern versions of Microsoft Word: 2010, 2013, and 2016. Microsoft Word Perform the following steps each time you plan to distribute a final electronic copy of a Word document: Save a copy of your document by clicking the File tab and selecting Save As.Then select where you want to save the file, type a name in the File Name box and click Save.; In your original document, click the File tab and then click Info.
-->Applies to: Azure Information Protection, Office 365
Note
To provide a unified and streamlined customer experience, Azure Information Protection client (classic) and Label Management in the Azure Portal are being deprecated as of March 31, 2021. This time-frame allows all current Azure Information Protection customers to transition to our unified labeling solution using the Microsoft Information Protection Unified Labeling platform. Learn more in the official deprecation notice.
Have a question about Azure Information Protection that is specifically about classification and labeling? See if it's answered here.
Which client do I install for testing new functionality?
Currently, there are two Azure Information Protection clients for Windows:
'Independent Advisors' work for contractors hired by Microsoft. I am an unpaid volunteer and do not work for Microsoft. Free microsoft for mac trial.
The Azure Information Protection unified labeling client that downloads labels and policy settings from one of the following admin centers: Office 365 Security & Compliance Center, Microsoft 365 security center, Microsoft 365 compliance center. This client is now in general availability, and might have a preview version for you to test additional functionality for a future release.
The Azure Information Protection client (classic) that downloads labels and policy settings from the Azure portal. This client builds on previous general availability versions of the client.
We recommend you test with the unified labeling client if its current feature set and functionality meet your business requirements. If not, or if you have configured labels in the Azure portal that you haven't yet migrated to the unified labeling store, use the classic client.
For more information, including a feature and functionality comparison table, see Choose which Azure Information Protection client to use.
Where can I find information about using sensitivity labels for Office apps?
See the following documentation resources:
Can a file have more than one classification?
Users can select just one label at a time for each document or email, which often results in just one classification. However, if users select a sublabel, this actually applies two labels at the same time; a primary label and a secondary label. By using sublabels, a file can have two classifications that denote a parentchild relationship for an additional level of control.
For example, the label Confidential might contain sublabels such as Legal and Finance. You can apply different classification visual markings and different Rights Management templates to these sublabels. A user cannot select the Confidential label by itself; only one of its sublabels, such as Legal. As a result, the label that they see set is Confidential Legal. The metadata for that file includes one custom text property for Confidential, one custom text property for Legal, and another that contains both values (Confidential Legal).
When you use sublabels, don't configure visual markings, protection, and conditions at the primary label. When you use sublevels, configure these setting on the sublabel only. If you configure these settings on the primary label and its sublabel, the settings at the sublabel take precedence.
How do I prevent somebody from removing or changing a label?
Although there's a policy setting that requires users to state why they are lowering a classification label, removing a label, or removing protection, this setting does not prevent these actions. To prevent users from removing or changing a label, the content must already be protected and the protection permissions do not grant the user the Export or Full Control usage right.
When an email is labeled, do any attachments automatically get the same labeling?
No. When you label an email message that has attachments, those attachments do not inherit the same label. The attachments remain either without a label or retain a separately applied label. However, if the label for the email applies protection, that protection is applied to Office attachments.
How can DLP solutions and other applications integrate with Azure Information Protection?
Because Azure Information Protection uses persistent metadata for classification, which includes a clear-text label, this information can be read by DLP solutions and other applications.
For more information about this metadata, see Label information stored in emails and documents.
For examples of using this metadata with Exchange Online mail flow rules, see Configuring Exchange Online mail flow rules for Azure Information Protection labels.
Can I create a document template that automatically includes the classification?
Yes. You can configure a label to apply a header or footer that includes the label name. But if that doesn't meet your requirements, for the Azure Information Protection client (classic) only, you can create a document template that has the formatting you want and add the classification as a field code.
As an example, you might have a table in your document's header that displays the classification. Or, you use specific wording for an introduction that references the document's classification.
To add this field code in your document:
Microsoft Metadata Services
Label the document and save it. This action creates new metadata fields that you can now use for your field code.
In the document, position the cursor where you want to add the label's classification and then, from the Insert tab, select Text > Quick Parts > Field.
In the Field dialog box, from the Categories dropdown, select Document Information. Then, from the Fields names dropdown, select DocProperty.
From the Property dropdown, select Sensitivity, and select OK.
The current label's classification is displayed in the document and this value will be refreshed automatically whenever you open the document or use the template. So if the label changes, the classification that is displayed for this field code is automatically updated in the document.
How is classification for emails using Azure Information Protection different from Exchange message classification?
Exchange message classification is an older feature that can classify emails and it is implemented independently from Azure Information Protection labels or sensitivity labels that apply classification.
However, you can integrate this older feature with labels, so that when users classify an email by using Outlook on the web and by using some mobile mail applications, the label classification and corresponding label markings are automatically added.
You can use this same technique to use your labels with Outlook on the web and these mobile mail applications.
Note that there's no need to do this if you're using Outlook on the web with Exchange Online, because this combination supports built-in labeling when you publish sensitivity labels from the Office 365 Security & Compliance Center, Microsoft 365 security center, or Microsoft compliance center.
If you cannot use built-in labeling with Outlook on the web, see the configuration steps for this workaround: Integrate Exchange message classification with Azure Information Protection for a mobile device labeling solution.
-->Do you want to create a solution that extends the functionality of Word? For example, one that involves automated document assembly? Or a solution that binds to and accesses data in a Word document from other data sources? You can use the Office Add-ins platform, which includes the Word JavaScript API and the Office JavaScript API, to extend Word clients running on a Windows desktop, on a Mac, or in the cloud.
Word add-ins are one of the many development options that you have on the Office Add-ins platform. You can use add-in commands to extend the Word UI and launch task panes that run JavaScript that interacts with the content in a Word document. Any code that you can run in a browser can run in a Word add-in. Add-ins that interact with content in a Word document create requests to act on Word objects and synchronize object state.
Note
If you plan to publish your add-in to AppSource and make it available within the Office experience, make sure that you conform to the Commercial marketplace certification policies. For example, to pass validation, your add-in must work across all platforms that support the methods that you define (for more information, see section 1120.3 and the Office Add-in host and availability page).
The following figure shows an example of a Word add-in that runs in a task pane.
Microsoft word scrolling mac. Figure 1. Add-in running in a task pane in Word
The Word add-in (1) can send requests to the Word document (2) and can use JavaScript to access the paragraph object and update, delete, or move the paragraph. For example, the following code shows how to append a new sentence to that paragraph.
You can use any web server technology to host your Word add-in, such as ASP.NET, NodeJS, or Python. Use your favorite client-side framework -- Ember, Backbone, Angular, React -- or stick with VanillaJS to develop your solution, and you can use services like Azure to authenticate and host your application.
The Word JavaScript APIs give your application access to the objects and metadata found in a Word document. You can use these APIs to create add-ins that target:
- Word 2013 or later on Windows
- Word on the web
- Word 2016 or later on Mac
- Word on iPad
Write your add-in once, and it will run in all versions of Word across multiple platforms. For details, see Office Add-in host and platform availability.
JavaScript APIs for Word
You can use two sets of JavaScript APIs to interact with the objects and metadata in a Word document. The first is the Common API, which was introduced in Office 2013. Many of the objects in the Common API can be used in add-ins hosted by two or more Office clients. This API uses callbacks extensively.
The second is the Word JavaScript API. This is a strongly-typed object model that you can use to create Word add-ins that target Word 2016 on Mac and Windows. This object model uses promises, and provides access to Word-specific objects like body, content controls, inline pictures, and paragraphs. The Word JavaScript API includes TypeScript definitions and vsdoc files so that you can get code hints in your IDE.
Currently, all Word clients support the shared Office JavaScript API, and most clients support the Word JavaScript API. For details about supported clients, see Office Add-in host and platform availability.
View Word Metadata Mac
We recommend that you start with the Word JavaScript API because the object model is easier to use. Use the Word JavaScript API if you need to:
- Access the objects in a Word document.
Use the shared Office JavaScript API when you need to:
- Target Word 2013.
- Perform initial actions for the application.
- Check the supported requirement set.
- Access metadata, settings, and environmental information for the document.
- Bind to sections in a document and capture events.
- Use custom XML parts.
- Open a dialog box.
How To View Microsoft Word Metadata
Next steps
Ready to create your first Word add-in? See Build your first Word add-in. Use the add-in manifest to describe where your add-in is hosted, how it is displayed, and define permissions and other information.
To learn more about how to design a world class Word add-in that creates a compelling experience for your users, see Design guidelines and Best practices.
After you develop your add-in, you can publish it to a network share, an app catalog, or AppSource.