Microsoft Word For Mac V 16 Removing Metadata
Introduction
Quit out of all Office for Mac apps such as Word, Excel, PowerPoint, Outlook, and OneNote. Search for 'keychain' in Spotlight and launch the Keychain Access app. Select the login keychain entry in the top left navigator pane, then from the File menu, choose Lock Keychain 'login'. Fortunately, we can help! Here are our tips, tricks, and tutorials for Microsoft Word. How to Get Microsoft Word. Microsoft Word is bundled with Office 365, which also includes Outlook, Excel, PowerPoint, OneNote, OneDrive, and more. You can’t get Word on its own, but an Office 365 subscription with Word is just $8.25/month, and you can.
Metadata is simply 'data about data.' Within the context of the computer industry, the most common domain of metadata is the file system. Files contain data, which has some amount of associated metadata. The most fundamental property of metadata is that it is distinct from the data itself. Again, that is the very definition of metadata: data about data.
It's a simple concept, but it's also a surprisingly fertile topic for debate. The introduction of Mac OS X has brought this topic to the forefront of the larger battle for the future of the Mac platform. To understand why, we'll examine the fundamentals of file metadata (or simply 'metadata' henceforth), and explore the past, present, and future of metadata on the Mac, and in the computer industry as a whole.
There is one important assumption to keep in mind. This article will generally confine itself to the contemporary concept of files and file systems. Object-relational storage or other such divergences from the familiar files and directories common today will be touched upon in later sections, but will not be considered in the main body of the article in order to keep the focus manageable.
There are also some assumptions to avoid. The first part of this article will talk about the fundamental concepts of metadata, irrespective of any implementation issues (with the exception of the single, focus-narrowing assumption listed above). While reading about the fundamentals of metadata, technically inclined readers (that's everyone who reads Ars, right? ;-) may find it very difficult to avoid slipping into thoughts of actual implementations they are familiar with. Don't do this. Try to concentrate on the concepts being presented without making judgments or coming to conclusions based on particular implementations or standards you may be familiar with. We'll get to all that later in the article, after the fundamentals have been established.
Fundamentals
To illustrate the fundamentals of metadata, let's start with a hypothetical file. Without any metadata, this file is just data: a bunch of bits. What kind of 'data about this data' can we come up with? Let's make a list.
- The file's name. This is an essential piece of metadata, given the assumption listed earlier regarding the concept of a file. A file's name is an essential part of the access mechanism in a traditional file system.
- The file's location. We need more than just the name to uniquely select a file in a traditional file system. A file's location is some combination of the host, disk, and directory structure where the file is located. A file may be uniquely selected by combining the file's name and the file's location into a single identifier (often called the 'path' to the file).
Most people are not accustomed to thinking about a file's location as a piece of metadata associated with the file itself. This is your first test: are you thinking about 'data about data' at the conceptual level, or have you already slipped into an implementation mindset and snorted derisively at the idea of file locations as metadata?
Think about it. A file's location is certainly 'data about the data.' In fact, it's essential data about the data. (We'll make some distinctions about different types of metadata later.)
- The nature of the file's data. What does the file's data represent? What is the file? Is it an image? A movie? Text? This concept is also called the file's 'content type' or just the file's 'type.' There are many levels of detail possible, from basic classification (image, audio, video, text, etc.) to specific file 'formats' (JPEG, AIFF, MPEG2, Microsoft Word, etc.), or even very specific incarnations of particular formats (GIF89a, Photoshop document with layers, Microsoft Word 6.0/95, etc.)
- The file's size. The data in a file has a size, even if it's zero. Again, this is not what most people think about when they think of metadata, but it most certainly fits the bill. Like file name and location, it's another essential piece of information about the file. (Imagine the limitations of a file system where a file's size was unknown!)
- File dates. There are many useful dates one can imagine associating with a file: creation date, date of last data modification, date of last metadata modification, date of last data access, and so on.
- File permissions. Like file dates, there are many possible variants of this metadata. Who can read this file? Who can write to it? Who can run it, if it's executable? Etc.
I'm going to stop the list now, but not because it's in any way complete. I'm sure you can think of many more pieces of metadata that are applicable to a file, especially if you focus on metadata that may only be applicable to particular types of files. For our purposes, I just wanted to cover a set of basic metadata that spans a conceptual range, which we'll explore next.
Types of Metadata
Take another look at the short list of file metadata we came up with:
- Name
- Location
- Type
- Size
- Dates
- Permissions
If you had to divide this list into groups, how would you do it? Are there certain pieces of metadata that share common traits? Think about it before continuing.
<pause for thought>
Let's start with permissions. This is metadata in the traditional sense familiar to most people. It describes the access rights for the data (in some implementation-specific way that you shouldn't be concerned with right now, remember? :-)
The nature of file permissions as metadata is best illustrated by changing them. Despite the fact that file permissions are indeed data about the file's data (who/what can do XYZ to this data?), they may be changed without regard for the data itself.
What other pieces of metadata from our list share this quality? Name and location seem to fit the bill. Changing a file's location, for example, does not imply a change to the file's data.
Some file dates also exhibit this quality. Creation date and possibly the last access data (assuming read-only access) also may change with complete independence from the data that they are associated with. (Modification date, on the other hand, should not change unless the data itself has been (duh) modified.)
We'll call these pieces of metadata (name, location, permissions, and some kinds of dates) 'independent metadata' to signify their ability to be changed independent of any changes to the data itself.
We've already grouped more than half the list ('three and a half' out of the six) into this category. Independent metadata is the most common type of metadata. Almost all metadata can be changed without requiring changes to the data itself. But independednt metadata is not necessarily the most important type of metadata. Let's look at another type, using file size as our first example.
Size is an essential piece of metadata, but like location, it is rarely thought of as metadata. Why is that? Perhaps it's because it's so essential that its presence is taken for granted. After all, if the extent of the file (i.e. its size) cannot be determined, the file is nearly useless! For example, how would the operating system know when to stop reading data from a file without any information about its size?
A file's size is an example of what I'm going to call 'immutable metadata' in that in that it is metadata that cannot change for any given set of data. In other words, immutable metadata may not change unless the data itself also changes. Immutable metadata can also be thought of as 'data-dependent' metadata, but I have chosen to call it 'immutable' to emphasize that it cannot be changed directly. The immutable metadata associated with a given set of bits (i.e. data) is indeed immutable. The only way to get different immutable metadata is to get different data.
Think about the consequences of violating the constraints of immutable metadata. Imagine a scenario in which the 'size' metadata for a file was changed without any change to the actual data! Immutable metadata is worse than useless if it is not completely tied to the state of the data itself.
The concept of a file's size as 'immutable metadata' may be difficult to get your head around, particularly since we're so used to thinking of a file's size as something that is 'derived from' the data itself, rather than simply 'associated with' the data like the independent metadata described earlier. But that's the very definition of immutable metadata: it is metadata that is inexorably tied to the data itself.
Modification date was touched on earlier, and is another example of immutable metadata. The modification date is changed in response to an accompanying change to the data itself. Changing a file's modification date without changing the data itself is not as disastrous as doing the same thing to a file's size metadata, but it is certainly not 'correct' behavior.
Finally, there's the file's content type. This too is immutable metadata. A file's content type, by definition, cannot change unless the data itself also changes.
Thoughtful readers may have already realized that there is one case where immutable metadata may change without requiring a change to the data itself. Immutable metadata may change to increase (or decrease, of course) its accuracy. For example, a file may have associated file type metadata that identifies it as a GIF image. At some point in the future, it may become known that the file is actually an interlaced GIF89a. The file type metadata may be changed to reflect this increased accuracy without requiring a change to the data itself. Similarly, a file's modification date may be increased to millisecond accuracy, and so on.
This leads to some more general rules for metadata. Like all forms of information, more is generally better. More metadata with greater detail makes more interesting decisions possible. Without permissions metadata, for example, it is much more difficult to make intelligent decisions regarding access to a file's data. And if a file's creation date only includes the year, it becomes impossible to distinguish the relative ages of files created within a given year. Information is power.
One final note on metadata which may seem obvious, but which will become a factor later on. Like all forms of information, metadata is easy to remove or ignore, but it is often difficult (or impossible) to add once it is lost. If you no longer know when a file was last modified, you cannot recover that piece of information (despite the fact that the modification date is immutable metadata completely tied to the data itself). The data itself remains, but the information about when that data was last modified is lost. To use an analogy, think of lossy compression. You can convert a CD track into an MP3 file, but you cannot convert an MP3 file back into the uncompressed audio from the CD. You cannot 'add' unknown information. Information is precious.
-->Office add-ins help you personalize your documents and streamline the way you access information on the web (see Start using your Office Add-in). As an admin, you can deploy Office add-ins for the users in your organization. You can do this using the Centralized Deployment feature in the Microsoft 365 admin center.
Centralized Deployment is the recommended and most feature-rich way for most admins to deploy add-ins to users and groups within an organization. For more information on how to determine if your organization can support Centralized Deployment, see Determine if Centralized Deployment of add-ins works for your Office 365 organization.
Centralized Deployment provides the following benefits:
To switch Identities in Outlook 2011 for Mac, take these steps: Quit Outlook (pressing Command-Q quits any application). Run the Microsoft Database Utility. Change the default Outlook Identity. Click the red close window button in the upper-left corner of. Feb 08, 2019 Make sure you have 2011 updated to 14.7.7 before you open it with your moved Microsoft User Data folder. The first time you open Outlook it will rebuild your existing identity. The first time you open Outlook it will rebuild your existing identity. Switch the identity used by Outlook. Close Outlook. Open the Microsoft Database Utility. The default location is in /Applications/Microsoft Office 2011/Office/. Tip: You can also open the Database. Click the identity that you want, click Action, and then click Set as Default. Open Outlook. 
Inside the Office 2011 Identities folder, Outlook stores one folder for each individual Identity. The name of the folder is the name of the Identity. Each Identity folder stores your e-mail, account information, calendar events, tasks, and notes in a database for each Identity.
A Global admin can assign an add-in directly to a user, to multiple users via a group, or to everyone in the tenant.
When the relevant Office application starts, the add-in automatically downloads for the user. If the add-in supports add-in commands, the add-in automatically appears in the Ribbon within the Office application.
Add-ins will no longer appear for users if the admin turns off or deletes the add-in, or if the user is removed from Azure Active Directory or from a group that the add-in is assigned to.
Note
For Word, Excel and PowerPoint use a SharePoint App Catalog to deploy add-ins to users in an on-premises environment with no connection to Office 365 and/or support for SharePoint add-ins required. > For Outlook use Exchange control panel to deploy in an on-premises environment without a connection to Office 365. >
Recommended approach for deploying Office add-ins
Consider rolling out add-ins in a phased approach to help ensure your add-in deployment goes smoothly. We recommend the following plan:
Roll-out the add-in to a small set of business stakeholders and members of the IT department. Evaluate if the deployment was successful, and if so, move on to step 2.
Roll-out to a larger set of individuals within the business who will be using the add-in. Again, evaluate results and, if all went well, go to the next step of a full deployment.
Full rollout to target audience of users.
Depending on the size of the target audience, you may want to add or remove roll-out steps.
Deploy an Office add-in using the admin center
Before you begin, see Determine if Centralized Deployment of add-ins works for your Office 365 organization.
In the Microsoft 365 admin center, go to the Settings > Add-ins page.
Select Deploy Add-in at the top of the page. On the overview page, select Next.
Select an option and follow the instructions.
If you selected the option to add an add-in from the Office Store, you can now make your add-in selection. Notice that you can view available add-ins via categories of Suggested for you, Rating, or Name. Only free add-ins are available to add from the Office Store. Paid add-ins aren't supported currently. Once you've selected your add-in, you will need to agree to some additional terms and conditions in order to proceed.
NOTE: With the Office Store option, updates and enhancements to the add-in will automatically be made available to users without your intervention.On the next page, select Everyone, Specific users/groups or Just me to specify who the add-in is deployed to. Use the Search box to find the users or groups who you want to deploy the add-in to.
NOTE: Learn about the other states that apply to an add-in. See Add-in states later in this topic. Microsoft doc viewer mac torrent.Select Deploy.
A green tick will appear when the add-in has been deployed. You can follow the on-page instructions to test that the add-in has deployed successfully.
Note
Users may need to relaunch Office to see the add-in icon appear on the ribbon of app. Outlook add-ins can take up to 24 hours to appear on users' ribbons.
- When finished, select Next. If you've deployed to just yourself, you can select Change who has access to add-in in order to deploy to more users.
If you've deployed the add-in to members of your organization other than yourself, follow the instructions displayed in order to effectively announce the deployment of the add-in.
You now see your add-in along with other apps in Office 365.
It's a good idea to inform the users and groups who you deployed the add-in to so that they know that it's available. Consider sending an email to them that describes when and how to use the add-in and explains how the add-in can help them do their job better. Include or link to relevant Help content or FAQs that might help if users have any problems with the add-in.
Considerations when assigning an add-in to users and groups
Admins can assign an add-in to everyone or to specific users and groups. Each option has implications:
Everyone: As the name implies, this option assigns the add-in to every user in the tenant. Use this option sparingly and only for add-ins that are truly universal to your organization.
Users: If you assign an add-in to an individual user, then to deploy the add-in to a new user, you will need to first add that user. The same goes for removing users.
Groups: If you assign an add-in to a group, users who are added to the group will automatically be assigned the add-in. And, when a user is removed from a group, the user loses access to the add-in. In either case, no additional action is required from you as the admin.
Just me: If you assign an add-in to just yourself, this assigns the add-in to only your account. This is ideal if you wish to test out the add-in first.
The option that is right for your organization depends on your configuration. However, we recommend making assignments via groups. As an admin, you might find it easier to manage add-ins using groups and control the membership of those groups rather than having to change the users assigned each time. On the other hand, in some situations, you may want to restrict access to a very small set of users and therefore make assignments to specific users. As a result, you will need to manage the assigned users manually.
Add-in states
Admins can turn on or off the add-ins they deploy for all users from the Microsoft 365 admin center.
- In the admin center, go to the Settings > Add-ins page.
- Select the deployed add-in.
- Click the Status toggle to turn the add-in On or Off.
- Save the changes.
One of three add-in states is also available.
| State | How the state occurs | Impact |
|---|---|---|
| Active | Admin uploaded the add-in and assigned it to users or groups. | Users and groups assigned to the add-in see it in the relevant clients. |
| Turned off | Admin turned off the add-in. | Users and groups assigned to the add-in no longer have access to it. If the add-in state is changed to Active, the users and groups will have access to it again. |
| Deleted | Admin deleted the add-in. | Users and groups assigned the add-in no longer have access to it. |
Consider deleting an add-in if no one is using it any more. Turning off an add-in may make sense if an add-in is used only during specific times of the year.
Security of Office add-ins
Office add-ins combine an XML manifest file that contains some metadata about the add-in, but most importantly points to a web application which contains all the code and logic. Add-ins can range in their capabilities. For example, add-ins can:
Display data.
Read a user's document to provide contextual services.
Read and write data to and from a user's document to provide value to that user.
For more information about the types and capabilities of Office add-ins, see Office Add-ins platform overview, especially the section 'Anatomy of an Office Add-in.'
To interact with the user's document, the add-in needs to declare what permission it needs in the manifest. A five-level JavaScript API access-permissions model provides the basis for privacy and security for users of task pane add-ins. The majority of the add-ins in the Office Store are level ReadWriteDocument with almost all add-ins supporting at least the ReadDocument level. For more information about the permission levels, see Requesting permissions for API use in content and task pane add-ins.
When updating a manifest, the typical changes are to an add-in's icon and text. Occasionally, add-in commands change. However, the permissions of the add-in do not change. The web application where all the code and logic for the add-in runs can change at any time, which is the nature of web applications.
Updates for add-ins happen as follows:
Line-of-business add-in: In this case, where an admin explicitly uploaded a manifest, the add-in requires that the admin upload a new manifest file to support metadata changes. The next time the relevant Office applications start, the add-in will update. The web application can change at any time.
Note
Admin does not need to remove a LOB Add-in for doing an update. In the Add-ins section, Admin can simply click on the LOB Add-in and choose the Update Button in the bottom right corner. Update will work only if the version of the new add-in is greater than that of the existing add-in.
Office Store add-in: When an admin selected an add-in from the Office Store, if an add-in updates in the Office Store, the add-in will update later in Centralized Deployment. The next time the relevant Office applications start, the add-in will update. The web application can change at any time.
Edit Add-in access
Download Microsoft Word For Mac
Post deployment, admins can also modify the user access to add-ins.
In the admin center, go to the Settings > Services & add-ins page.
Select the deployed add-in.
Click on Edit under Who has Access.
Save the changes.
Prevent add-in downloads by turning off the Office Store across all clients (Except Outlook)
Note
Outlook add-in installation is managed by a different process.
As an organization you may wish to prevent the download of new Office add-ins from the Office Store. This can be used in conjunction with Centralized Deployment to ensure that only organization-approved add-ins are deployed to users within your organization.
To turn off add-in acquisition:
In the admin center, go to the Settings > Services & add-ins page.
Select User owned apps and services.
Clear the option to let users access the Office store.
This will prevent all users from acquiring the following add-ins from the store.
Add-ins for Word, Excel, and PowerPoint 2016 from:
Windows
Mac
Office
Acquisitions starting within AppSource
Add-ins within Office 365
A user who tries to access the store will see the following message: Sorry, Office 365 has been configured to prevent individual acquisition of Office Store add-ins.
Support for turning off the Office Store is available in the following versions:
Windows: 16.0.9001 - Currently available.
Mac: 16.10.18011401 - Currently available.
iOS: 2.9.18010804 - Currently available.
The web - Currently available.
This does not prevent an administrator from using Centralized Deployment to assign an add-in from the Office Store.
To prevent a user from signing in with a Microsoft account, you can restrict logon to use only the organizational account. For more information, look here.
Minors and acquiring add-ins from the Store
The General Data Protection Regulation (GDPR) is a European Union regulation that becomes effective May 25, 2018. It gives users rights to and protection of their data. One of the aspects of the GDPR is that minors cannot have their personal data sent to parties that their parent or guardian hasn't approved. The specific age defined as a minor depends on the region where the individual is located.
Regions that have statutory regulations about parental consent include the United States, South Korea, the United Kingdom, and the European Union. For those regions, a minor will be blocked (via Azure Active Directory) from getting any new Office add-ins from the Store and running add-ins that were previously acquired. For countries without statutory regulations, there will be no download restrictions.
A user is determined to be a minor based on data specified in Azure Active Directory. The tenant admin is responsible for declaring the legal age group and the parental consent for that user.
If the parent/guardian consents to a minor using a specific add-In, then the tenant admin can use centralized deployment to deploy that add-In to all minors who have consent.
To be GDPR compliant for minors you need to ensure that one of following builds of Office is deployed in your school/organization.
Sog
For Word, Excel, PowerPoint, and Project:
| Platform | Build number |
| Office 2016 ProPlus Monthly for Windows | 9001.2138 |
| Office 2016 ProPlus Semi-Annual | 8431.2159 |
| Office 2016 for Windows | 16.0.4672.1000 |
| Office 2013 for Windows | 15.0.5023.1000 |
| Office 2016 for Mac | 16.11.18020200 |
| Office for the web | N/A |
For Outlook:
Macv Vietnam
| Platform | Build number |
| Outlook 2016 for Windows (MSI) | Build No TBD |
| Outlook 2016 for Windows (C2R) | 16.0.9323.1000 |
| Office 2016 for Mac | 16.0.9318.1000 |
| Outlook mobile for iOS | 2.75.0 |
| Outlook mobile for Android | 2.2.145 |
| Outlook.com | N/A |
Office 2013 requirements
Word, Excel, and PowerPoint 2013 for Windows will support the same minor checks if Active Directory Authentication Library (ADAL) is enabled. There are two options for compliance, as explained next.
Enable ADAL. This article explains how to enable ADAL for Office 2013: Using Office 365 modern authentication with Office clients.
You also need to set the registry keys to enable ADAL as explained in Enable Modern Authentication for Office 2013 on Windows devices.
Additionally, you need to install the following April updates for Office 2013:Don't enable ADAL. If you're unable to enable ADAL in Office 2013, then our recommendation is to use Group Policy to turn off the Store for the office clients. Information on how to turn off the app for Office settings is located here.
End user experience with add-ins
Now that you've deployed the add-in, your end users can start using it in their Office applications (see Start using your Office Add-in). The add-in will appear on all platforms that the add-in supports.
If the add-in supports add-in commands, the commands appear on the Office ribbon. In the following example, the command Search Citation appears for the Citations add-in.
Microsoft Word And Excel For Mac
If the deployed add-in doesn't support add-in commands or if you want to view all deployed add-ins, you can view them via My Add-ins.
In Word 2016, Excel 2016, or PowerPoint 2016
Select Insert > My Add-ins.
Select the Admin Managed tab in the Office Add-ins window.
Double-click the add-in you deployed earlier (in this example, Citations ).
In Outlook
On the Home ribbon, select Get Add-ins.
Select Admin-managed in the left nav.
Delete the add-in
You can also delete an add-in that was deployed.
In the admin center, go to the Settings > Services & add-ins page.
Select the deployed add-in.
Click on Delete Add-In. Remove the Add-in button on the bottom right corner.
Validate your selections, and choose Remove add-in.
Learn more
Learn more about creating and building Office Add-ins.
Use Centralized Deployment PowerShell cmdlets to manage add-ins.