2019-1-2 It is not feasible to disable the Cloud Fonts in Office for Mac. For your reference: Cloud fonts in Office. Considering it's a new feature, we will keep improving it. For any feedback, please feel free to share at Word for Mac UserVoice.Use #CloudFonts if your comment is about cloud fonts or #Typography if your comment is related to the font. Update Office from the Mac App Store. If you downloaded Office from the Mac App Store, and have automatic updates turned on, your apps will update automatically. But you can also manually download the updates: Open the Mac App Store from your Dock or Finder. MICROSOFT OFFICE 365 MAC OSX OFFICE CLOUD 10) A summary page will show once the installation is complete, click on the Close button to begin using Office 2011 for Mac. Microsoft Office 365 related websites Install Office using Office 365 for business Office in education Microsoft Office for Mac how-to. Familiarity, compatibility and a rich set of features for power users are the main benefits of opting for Office on your Mac. If your office is a Microsoft shop it will probably be easiest to use.
When you enable this capability, we will sync your Google account to the Microsoft Cloud. This means that a copy of your email, calendar, and contacts will be synchronized between Google and Microsoft data centers. Having your mailbox data in the Microsoft Cloud lets you use the new features of Outlook 2016 for Mac with your Gmail account.
Applies to:Office for Mac, Office 2019 for Mac, Office 2016 for Mac
After Office for Mac is installed, users can configure settings for the apps. These settings are called preferences. As an admin, you might want to provide Office for Mac users in your organization with a standard set of preferences. For example, you can configure how often to check for software updates for Office for Mac - daily, weekly, or monthly.
Preferences for Office for Mac are stored in preference files. These files are often referred to as .plist files.
There are changes in Office for Mac to improve security, including implementing Apple app sandboxing guidelines. These changes mean that you can't customize the app bundle before or after you deploy Office. But, preference files aren't part of the app bundle for an app, so you can make changes to these files.
Preference files are stored in the app container, which isn't the same thing as the app bundle. The app container is created the first time an app is run. The app container is located in the user's ~/Library/Containers folder. For example, the app container for Excel is named com.microsoft.Excel. Within the app container, the .plist file is located in the Data/Library/Preferences folder. For example, the .plist file for Excel is named com.microsoft.Excel.plist.
The best way to add or edit preferences is by using the defaults command. For example, if you want to configure updates to be checked manually, you can open Terminal and enter the following command:
You can take an existing .plist file and modify it with your organization's preferences. In some cases, you can actually copy that .plist file to other computers in your organization that have Office for Mac installed. But that doesn't work in the case of all .plist files. Therefore, the preferred method is to create a script that incorporates all the defaults commands that you want to use to set preferences. Then deploy that script to your users. The script needs to be run in the user's context, because preferences are user specific. That also means that if several users share the same computer and each has a different login account, then the script needs to be run for each user of that computer.
Depending on which preferences you're configuring and how you deploy those preferences, the user might need to quit all Office apps and restart the computer for the preferences to take effect. Also, remember that the preferences you deploy might overwrite existing preference settings configured by the user.
Office for Mac 2011, which is no longer supported, also used preference files. There are some preferences in common between Office for Mac and Office for Mac 2011. Therefore, if you install Office for Mac on a computer that has Office for Mac 2011 installed, Office for Mac will automatically inherit some preference settings from the Office for Mac 2011 installation.
Office 365 ProPlus is being renamed to Microsoft 365 Apps for enterprise. To learn more about this name change, read this blog post.
For details of when this change takes effect, and what actions admins might need to take, read this article.
Follow the steps in this article to deploy Office 365 ProPlus to client computers from the Office Content Delivery Network (CDN) by using the Office Deployment Tool (ODT).
Before you begin
Make sure your users have local admin privileges on their client devices. If that is not the case, then you should use your standard deployment tools and processes to install Office.
If you haven't already, complete the assessment and planning phases for your Office deployment.
This article is intended for administrators in enterprise environments working with hundreds or thousands of computers. If you want to install Office on a single device or small number of devices, we recommend reviewing Download and install or reinstall Office 365 or Office 2019 on your PC or Mac or Use the Office offline installer.
The steps in this article are based on the following best practices:
- Manage updates to Office automatically, without any administrative overhead. For more details, see Choose how to manage updates.
- Build two Office installation packages: Semi-Annual Channel for 64-bit and Semi-Annual Channel (Targeted) for 64-bit. Each installation package includes all the core Office apps. (If you want to deploy the 32-bit version of Office as well, you can create additional installation packages.) For more details, see Define your source files.
- Deploy to two deployment groups: a pilot group that receives the Semi-Annual Channel (Targeted) and a broad group that receives the Semi-Annual Channel. Note that in this scenario, the installation packages and deployment groups match exactly. In more complex deployments, you might have multiple deployment groups that use the same installation package. For more details, see Choose your update channels.
You can customize these options to match the requirements for your organization, including deploying to more than two groups, changing update channels, and deploying Visio and Project. For more details, see Customize your deployment.
Step 1: Download the Office Deployment Tool
You use the Office Deployment Tool (ODT) to deploy Office from the Office CDN. The deployment tool is run from the command line and uses a configuration file to determine what settings to apply when deploying Office.
Create the shared folder ServerShareO365 and assign read permissions for your users. For details about how to create shared folders and assign permissions, see Shared Folders.
Download the Office Deployment Tool from the Microsoft Download Center to ServerShareO365. If you've already downloaded the ODT, make sure you have the latest version.
After downloading the file, run the self-extracting executable file, which contains the Office Deployment Tool executable (setup.exe) and a sample configuration file (configuration.xml).
Step 2: Create a configuration file for the pilot group
To download and deploy Office 365 ProPlus to the pilot group, you use a configuration file with the ODT. To create the configuration file, we recommend using the Office Customization Tool.
- Go to Office Customization Tool and configure the desired settings for your Office 365 installation. We recommend the following options:
- Products: Office 365 ProPlus. You can also include Visio and Project if you plan to deploy those apps.
- Update channel: Choose Semi-Annual Channel (Targeted) for the installation package for the pilot group
- Language: Include all the language packs you plan to deploy. We recommend selecting Match operating system to automatically install the same languages that are in use by the operating system and any user on the client device. We also recommend selecting Fallback to the CDN to use the Office CDN as a backup source for language packs.
- Installation: Select Office Content Delivery Network (CDN).
- Updates: To update your client devices automatically, choose CDN and Automatically check for updates.
- Upgrades: Choose to automatically remove all previous MSI versions of Office. You can also choose to install the same language as any removed MSI versions of Office, but make sure to include those languages in your installation package.
- Additional properties: To silently install Office for your users, choose Off for the Display level and On for the Automatically accept the EULA.
- Application preferences: Define any Office settings you want to enable, including VBA macro notifications, default file locations, and default file formats
- When you complete the configuration, click Export in the upper right of the page, and then save the file as config-pilot-SACT.xml in the ServerShareO365 folder.
For more details on how to use the Office Customization Tool, see Overview of the Office Customization Tool. For more information about the configuration options, see Configuration options for the Office Deployment Tool.
Note that the Office installation files and Office updates will come from Semi-Annual Channel (Targeted). For more details on the most recent version of Office based on the different update channels, see Release information for updates to Office 365 ProPlus.
Step 3: Create a configuration file for the broad group
Using the Office Customization Tool, create the configuration file for the broad group.
- Go to Office Customization Tool and configure the desired settings for your Office 365 installation. We recommend matching the same options as the pilot group in Step 2, except for the following change:
- Update channel: Choose Semi-Annual Channel for the installation package for the broad group
- When you complete the configuration, click Export in the upper right of the page, and then save the file as config-pilot-SAC.xml in the ServerShareO365 folder.
This configuration file is used to download Office installation files and then deploy them to the broad group. The settings are exactly the same as the first configuration file, except the update channel is set to Semi-Annual Channel ('Broad').
Step 4: Deploy Office to the pilot group
To deploy Office, you provide commands that users can run from their client computers. The commands run the ODT in configure mode and with a reference to the appropriate configuration file, which defines which version of Office to install on the client computer. Users who run these commands must have local admin privileges and must have read permissions to the share (servershareO365).
From the client computers for the pilot group, run the following command from a command prompt with admin privileges:
ServerShareO365setup.exe /configure ServerShareO365config-pilot-SACT.xml
Most organizations will use this command as part of a batch file, script, or other process that automates the deployment. In those cases, you can run the script under elevated permissions, so the users will not need to have admin privileges on their computers.
After running the command, the Office installation should start immediately. If you run into problems, make sure you have the newest version of the ODT and make sure your configuration file and command reference the correct location. You can also troubleshoot issues by reviewing the log file in the %temp% and %windir%temp directories.
After Office has deployed to the pilot group, you can test Office in your environment, particularly with your hardware and device drivers. For more details, see Choose your update channels.
Step 5: Deploy Office to the broad group
After you've finished testing Office with the pilot group, you can deploy it to the broad group. To do so, run the following command from a command prompt with admin privileges:
ServerShareO365setup.exe /configure ServerShareO365config-broad-SAC.xml
This command is the same as the pilot group, except that it references the configuration file for the broad group. After running the command, the Office installation should start immediately.
Customize your deployment
The steps in this article cover the standard best practice recommendations from Microsoft. This section covers the most common customizations to these best practices.
Where Is Microsoft Office Cloud On Mac Computer
Build and deploy multiple packages to multiple deployment groups
If you want to deploy both the 32-bit and the 64-bit version of Office, you can create additional installation packages. (Two different architectures cannot be included in the same package.) For more details, see Define your source files.
Use different update channels for Office
With Office 365 ProPlus, you can control how frequently your users receive feature updates to their Office applications. To do so, you choose an update channel for your users. In this article, we recommend the Semi-Annual Channel (Targeted) for your pilot group and the Semi-Annual Channel for the rest of your organization. You can, however, choose the Monthly Channel, which provides users with the newest features of Office as soon as they're available. A single Office installation package can only include one type of channel, so each new channel requires an additional package. For more details, see Overview of update channels for Office 365 ProPlus.
Deploy Visio and Project alongside the core Office apps
To deploy Visio and Project with Office 365 ProPlus, you can include them as part of the Office application when building it in Configuration Manager. For more details on licensing and system requirements, see Deployment guide for Visio and Deployment guide for Project.