-->
- Group Policy To Deploy Software To Macs Free
- Group Policy To Deploy Software To Macs Mac
- Group Policy To Deploy Software To Macs Download
- Group Policy To Deploy Software To Macs Computer
In the past, Microsoft Teams was a separate installation from Microsoft 365 Apps. But starting with Version 1902, Teams is included as part of new installations of Microsoft 365 Apps. If Teams is already installed on the device, no changes are made to that installation of Teams.
Open the Group Policy Management Console. (Open the Run window type gpmc.msc press Enter). Right-click on the organizational unit where you need to deploy the Sophos Endpoint Security and Control software then select Create a GPO in this domain, and Link it here. Enter a GPO name. For example, Sophos Endpoint Security and Control. Sep 17, 2007 The oft confused 802.11x is nothing more than a generic representation of the group of wireless networking standards listed above. This really is a very substantial issue for many academic and business users, as access to their networks is typically controlled by an upstream Radius server and without support for configuring an 802.1X interface. We had to disable the public firewall in group policy before they would proceed. Surprise, it didn't fix the issue. Then he insisted it was AV. We uninstalled it and it didn't fix the issue. Then he insisted it was probably a Windows Update and we shouldn't just randomly patch machines. Apr 06, 2015 For company assigned iphones with company sim cards, we again apply the generic apple ID/icloud acount. Again, this is handy for people who like to lose their phones, we can track it down. We also use Meraki's (Free only for limited time when you evaluate one of their APs) to manage these devices (passwords, load software.etc.). I'm a.NET developer and want to write an IOS & Android app in C#. I've had a read around Xamarin for Visual Studio which looks interesting if not a tad expensive! Do you need a Mac to debug y.
Teams is also being added to existing installations of Microsoft 365 Apps on devices running Windows. For more information about when that occurs, see What about existing installations of Microsoft 365 Apps?.
Note
To complete the installation of Teams on new or existing installations of Microsoft 365 Apps, either restart the device or have the user log off and log back on.
If Skype for Business is already installed on the device, Skype for Business won't be removed and will continue to function as before. Skype for Business will continue to be installed with new installations of Microsoft 365 Apps, unless you configure your installation to exclude it.
God of war iso file for ppsspp emulator. You don't have to wait if you're ready now to deploy Teams to the users in your organization. You can deploy Teams for your users by following these instructions or you can have your users install Teams for themselves from https://teams.microsoft.com/downloads.
We also have the steps you can take to exclude Teams from new or existing installations of Microsoft 365 Apps if your organization isn't ready to deploy Teams.
Important
If you're in a GCC High or DoD environment, currently you need to exclude Teams from being installed with Microsoft 365 Apps. Instead, you need to install Teams by using the separate MSI-based installer. For links to the correct version of the MSI-based installer for your environment, see Install Microsoft Teams using Microsoft Endpoint Configuration Manager. In the future, you'll be able to install Teams along with Microsoft 365 Apps in GCC High or DoD environments without needing to use the separate MSI-based installer.
If you're using Office for Mac, see Microsoft Teams installations on a Mac.
If you're using shared computers or Virtual Desktop Infrastructure (VDI), see Shared computer and VDI environments with Microsoft Teams.
When will Microsoft Teams start being included with new installations of Microsoft 365 Apps?
The date when Teams starts being installed with new installations of Microsoft 365 Apps depends on which update channel you're using. The following table shows the schedule.
Update channel | Version | Date |
---|---|---|
Current Channel | Version 1902 | March 4, 2019 |
Monthly Enterprise Channel | Version 2003 | May 12, 2020 |
Semi-Annual Enterprise Channel (Preview) | Version 1902 | March 12, 2019 |
Semi-Annual Enterprise Channel | Version 1902 | July 9, 2019 |
Note
Teams is also included with the following new installations:
- Microsoft 365 Apps for business, starting with Version 1901, which was released on January 31, 2019. Microsoft 365 Apps for business is the version of Office that is included with some Microsoft 365 business plans, such as Microsoft 365 Business Premium.
- Office for Mac, starting with Version 16.21, which was released on January 16, 2019. Office for Mac comes with any plan that includes Microsoft 365 Apps. For more information, see Microsoft Teams installations on a Mac.
How to exclude Microsoft Teams from new installations of Microsoft 365 Apps
If you don't want Teams included when you install Microsoft 365 Apps on devices running Windows, you can use Group Policy or the Office Deployment Tool. Or, as an alternative, you can let Teams be installed, but use Group Policy to prevent Teams from automatically starting when the user signs in to the device.
If you want to use the Office Deployment Tool, you can use the ExcludeApp element in your configuration.xml file, as shown in the following example.
Tip
Instead of using a text editor to create your configuration.xml, we recommend that you use the Office Customization Tool (OCT). The OCT provides a web-based interface for making your selections and creating your configuration.xml file to be used with the Office Deployment Tool. For more information, see Overview of the Office Customization Tool.
If you're deploying Microsoft 365 Apps by using the Office 365 Client Installation wizard in Microsoft Endpoint Configuration Manager (current branch), you can set Teams to the Off position in the configuration UI.
If you're deploying Microsoft 365 Apps by using Microsoft Intune, there is a checkbox to exclude Teams on the Configure App Suite pane.
If you're letting your users install Microsoft 365 Apps for themselves from the Office 365 portal, you can't exclude Teams from being included as part of the installation, unless you use Group Policy.
To remove Teams after it's been installed, go to Control Panel > Uninstall a program and uninstall Microsoft Teams and any instances of Teams Machine-Wide Installer. If you previously installed Teams separately from installing Microsoft 365 Apps, you might see multiple instances of Teams Machine-Wide Installer. You can also use PowerShell to remove Teams as shown in this script sample.
What about existing installations of Microsoft 365 Apps?
Teams is also being added to existing installations of Microsoft 365 Apps on devices running Windows as part of the normal update process. Djay pro 1. 4. 3 mac download. There is no change to existing installations of Mac.
Whether Teams gets added to an existing installation of Microsoft 365 Apps is determined by what version is installed, what version you're updating to, and some other factors. Version 1906 that was released in Current Channel in July is the first version that started including Teams as part of the update process. But not all devices updating to Version 1906 or later have received Teams as part of the update process because the rollout has been a gradual process over several months. So if you've updated a device to the latest version of Microsoft 365 Apps, but Teams hasn't been installed, that is probably expected and not necessarily an error. It's likely a future update will install Teams. If you want Teams on that device now, you can install it manually from https://teams.microsoft.com/downloads.
Important
If you're updating your existing installation of Microsoft 365 Apps to Version 1908 (Build 11929.20300) or later, Teams will be added. To complete the installation of Teams after the update, either restart the device or have the user log off and log back on.
The date when Teams can start being added to existing installations of Microsoft 365 Apps depends on which update channel you're using. The following table shows the schedule.
Update channel | Version | Date |
---|---|---|
Current Channel | Version 1906 | July 9, 2019 |
Monthly Enterprise Channel | Version 2003 | May 12, 2020 |
Semi-Annual Enterprise Channel (Preview) | Version 1908 | September 10, 2019 |
Semi-Annual Enterprise Channel | Version 1908 | January 14, 2020 |
If you don't want Teams to be added to existing installations of Microsoft 365 Apps when you update to a newer version, you can use Group Policy or the Office Deployment Tool. Or, as an alternative, you can let Teams be added, but use Group Policy to prevent Teams from automatically starting when the user signs in to the device.
If you want to use the Office Deployment Tool, you need to run the Office Deployment Tool in /configure mode on each device before you update to the new version of Microsoft 365 Apps. The following is a configuration.xml file you can use with the Office Deployment Tool to exclude Teams from being added to your existing installation of Microsoft 365 Apps for enterprise.
Note
Group Policy To Deploy Software To Macs Free
- Be sure you're using the most current version of the Office Deployment Tool available on the Microsoft Download Center.
- If your existing installation of Microsoft 365 Apps has excluded other apps, such as Access, you need to include a line in your configuration.xmi file for each of those excluded apps. Otherwise, those apps will be installed on the device.
- If you have Microsoft 365 Apps for business installed, use O365BusinessRetail for the Product ID in your configuration.xml file.
Also, in some situations, doing an Online Repair results in Teams being installed. For example, if Microsoft 365 Apps is configured to get updates from the Office Content Delivery Network (CDN) and the update channel or version you're using includes Teams as part of the installation.
Use Group Policy to control the installation of Microsoft Teams
If your organization isn't ready to deploy Teams and you use Group Policy, you can enable the Don't install Microsoft Teams with new installations or updates of Office policy setting. You can find this policy setting under Computer ConfigurationPoliciesAdministrative TemplatesMicrosoft Office 2016 (Machine)Updates.
Note
- This policy setting only applies if you are installing or updating to Version 1905 or later of Microsoft 365 Apps.
- To use this policy setting, download at least version 4882.1000 of the Administrative Template files (ADMX/ADML), which were released on July 9, 2019.
If you enable this policy setting, Teams won't be installed in the following scenarios for Version 1905 or later:
- New installations of Microsoft 365 Apps
- Updates to existing installations of Microsoft 365 Apps
- Users installing Microsoft 365 Apps for themselves from the Office 365 portal
- An Online Repair of an existing installation of Microsoft 365 Apps
If you have Microsoft 365 Apps for business or can't use Group Policy for some other reason, you can add the preventteamsinstall value to the HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftOffice16.0commonofficeupdate key in the registry. The type for preventteamsinstall is REG_DWORD and the value should be set to 1 if you don't want Teams installed.
Use Group Policy to prevent Microsoft Teams from starting automatically after installation
If you want Teams to be installed, but don't want Teams to start automatically for the user after it's installed, you can use Group Policy and enable the Prevent Microsoft Teams from starting automatically after installation policy setting. You can find this policy setting under User ConfigurationPoliciesAdministrative TemplatesMicrosoft Teams.
By enabling this policy setting before Teams is installed, Teams won't start automatically when the user logs in to the device. Once a user signs in to Teams for the first time, Teams is configured to start automatically the next time the user logs into the device. The user can configure Teams to not start automatically by configuring user settings within Teams or by clearing the Open Teams on startup check box on the sign in screen for Teams.
Tip
If you've already installed Teams but you want to use this policy setting to prevent Teams from starting automatically, enable this policy setting and then run this script on a per-user basis to reset the autostart setting for Teams.
But even if you enable this policy setting so that Teams doesn't start automatically, an icon for Microsoft Teams will appear on the user's desktop.
Important
- This policy setting only applies if you are installing or updating to the following versions of Microsoft 365 Apps:
- Version 1906 or later of Current Channel
- Version 1902 (Build 11328.20368) or later of Semi-Annual Enterprise Channel or Semi-Annual Enterprise Channel (Preview)
- Version 2003 or later of Monthly Enterprise Channel
- To use this policy setting, download at least version 4882.1000 of the Administrative Template files (ADMX/ADML), which were released on July 9, 2019.
If you have Microsoft 365 Apps for business or can't use Group Policy for some other reason, you can add the PreventFirstLaunchAfterInstall value to the HKEY_CURRENT_USERSOFTWAREPoliciesMicrosoftOffice16.0Teams key in the registry. The type for PreventFirstLaunchAfterInstall is REG_DWORD and the value should be set to 1 if you don't want Teams to automatically start after installation.
Shared computer and VDI environments with Microsoft Teams
If devices in your organization are shared by multiple users, be aware that Teams is installed separately for each user that signs into that device. Installations of Teams average about 500 mb, so hard disk space, as well network bandwidth for updates, might become an issue for these shared devices installed with Teams. In cases where shared devices are used by a significant number of users, you might want to consider not installing Teams on those shared devices.
If you plan to use Teams in a Virtual Desktop Infrastructure (VDI) environment, see Teams for Virtualized Desktop Infrastructure. Teams installed with Microsoft 365 Apps as described in this article is NOT currently supported in VDI environments.
Feature and quality updates for Microsoft Teams
After Teams is installed, it's automatically updated approximately every two weeks with new features and quality updates. This update process for Teams is different than the update process for the other Office apps, such as Word and Excel. For more information, see Teams update process.
Microsoft Teams installations on a Mac
If you're using Version 16.21, or later, of the Office suite install package to deploy on a Mac, Teams will be included as part of the installation.
If you don't want Teams included as part of the installation, there is an Office suite install package available that doesn't include Teams. You can also use the install packages for individual applications, such as Word or Excel. For links to the most current install packages, see Update history for Office for Mac.
If you're letting your users install Office for themselves on a Mac, such as from https://teams.microsoft.com/downloads, you can't exclude Teams from being included as part of the installation.
To uninstall Teams on a Mac, quit Teams by right-clicking the Teams app in the dock, then hold down Option and choose Force Quit. Open the Application Folder, select Microsoft Teams, and move it to the Trash.
What about Office 365 plans that don't include Microsoft Teams?
Some Office 365 plans include Microsoft 365 Apps, but don't include the Teams service. Even if a plan doesn't include the Teams service, Teams will still be installed with Microsoft 365 Apps, as described earlier in this article. To prevent Teams from being installed, follow the steps outlined earlier in this article.
For Office 365 plans that don't include the Teams service, a free trial version of Teams that's valid for 1 year is available. Your users can start using it when they sign in to Teams. For more information about this free trial version and providing your users access to it, see Manage the Microsoft Teams Commercial Cloud Trial offer.
Additional information about installing Microsoft Teams
- There is no change to new or existing installations of Office 2019, such as Office Professional Plus 2019.
- Teams is installed with Microsoft 365 Apps in the same way that Teams is installed if you use the MSI-based installer for Teams. For each new user that signs into the device, the Teams installer runs and the Teams application is installed in the user's AppData folder.
- The architecture (sometimes referred to as the bitness) of Teams and Microsoft 365 Apps installed on the device don't have to match. For example, you can install the 32-bit version of Teams on a device running the 64-bit versions of Microsoft 365 Apps. To change the architecture of Teams, for example from 32-bit to 64-bit, you need to uninstall the 32-bit version of Teams and then install the 64-bit version of Teams.
- For more information for IT Pros about Microsoft Teams, see Microsoft Teams documentation.
If you plan to deploy Microsoft 365 Apps for enterprise (previously named Office 365 ProPlus) in a GCC High or DoD environment, there are some special considerations that you need to be aware of to help you meet your compliance requirements.
Which version of Microsoft 365 Apps for enterprise to deploy
Important
To meet GCC High and DoD compliance requirements, you must be running at least Version 1803 of Microsoft 365 Apps for enterprise.
Version 1803 or later is available in Current Channel, Monthly Enterprise Channel, Semi-Annual Enterprise Channel (Preview), and Semi-Annual Enterprise Channel.
What about other applications, such as Project and Visio?
You can deploy the subscription versions of the Project and Visio desktop apps in a GCC High or DoD environment, but they must be at least Version 1803. Any configuration or settings mentioned for Microsoft 365 Apps for enterprise also apply to the subscription versions of the Project and Visio desktop apps.
Outlook for iOS and Android is also available for GCC High or DoD environments. For more information, read this Tech Community blog post.
Important
For Teams, currently you need to exclude Teams from being installed when you install Microsoft 365 Apps for enterprise. Instead, you need to install Teams by using the separate MSI-based installer. In the future, you'll be able to install Teams along with Microsoft 365 Apps for enterprise without needing to use the separate MSI-based installer.
- For steps on how to exclude Teams from being installed with Microsoft 365 Apps for enterprise, see How to exclude Microsoft Teams from new installations of Microsoft 365 Apps and Use Group Policy to control the installation of Microsoft Teams.
- For links to the correct version of the MSI-based installer for your environment, see Install Microsoft Teams using Microsoft Endpoint Configuration Manager.
Which update channel of Microsoft 365 Apps for enterprise to use
We recommend Current Channel, because it provides your users with the newest Office features as soon as they are ready. If you need additional predictability of when these new Office features are released each month, we recommend Monthly Enterprise Channel. In those cases where you have select devices that require extensive testing before receiving new features, we recommend Semi-Annual Enterprise Channel.
For more information, see Overview of update channels for Microsoft 365 Apps.
Where to install Microsoft 365 Apps for enterprise from and where to get updates
If network connectivity and other considerations based on your organizational requirements aren't an issue, you can choose to deploy Microsoft 365 Apps for enterprise directly from the Office Content Delivery Network (CDN) on the internet. You can also configure Microsoft 365 Apps for enterprise to receive updates automatically from the Office CDN. This requires the least amount of administrative effort and is an easy way to keep Microsoft 365 Apps for enterprise up to date.
If you don't want computers installed with Microsoft 365 Apps for enterprise to connect to the Office CDN and the Device Management Service to get updates, you need to configure Microsoft 365 Apps for enterprise to be installed and updated from a shared folder from within your internal network. You will still need a least one computer to have access to the Office CDN to be able to download Microsoft 365 Apps for enterprise and updates to Microsoft 365 Apps for enterprise to the shared folder on your internal network. Also, computers installed with Microsoft 365 Apps for enterprise still require internet connectivity in order to remain activated.
Keep in mind that installing and updating Microsoft 365 Apps for enterprise from a shared folder on your local network requires significantly more administrative effort and more disk space. For example, you have to keep track of when new builds of Microsoft 365 Apps for enterprise are available and then download the updated version of Microsoft 365 Apps for enterprise to your network. The core files for Microsoft 365 Apps for enterprise are at least 1.6 GB and at least 250 MB for each language deployed.
If Microsoft 365 Apps for enterprise is being updated directly from the Office CDN, the amount of network traffic to each computer is significantly less, because only the changed files need to be downloaded. The size of those updates can vary from 50 mb to 300 mb. These estimates are based on historical data from the past year or so of updates.
What tools to use to deploy Microsoft 365 Apps for enterprise
There is no special guidance about what tools you can use to deploy Microsoft 365 Apps for enterprise in GCC High or DoD environments.
To deploy Microsoft 365 Apps for enterprise, you can use the Office Deployment Tool along with a configuration.xml file. The Office Deployment Tool is a command line tool, so it can be used with scripts or batch files. The configuration.xml file contains the settings for the installation. For example, where to install Microsoft 365 Apps for enterprise from, whether to install the 32-bit or 64-bit version, which languages to install, and where Microsoft 365 Apps for enterprise should connect to get updates. For more information about the Office Deployment Tool and the configuration.xml file, see Overview of the Office Deployment Tool and Configuration options for the Office Deployment Tool.
You can also use enterprise software deployment tools, such as Microsoft Endpoint Configuration Manager, to deploy Microsoft 365 Apps for enterprise. For more information about using Configuration Manager, see Deploy with Configuration Manager (current branch) and Deploy with Configuration Manager (2012 R2).
Note
If you have anti-virus or other endpoint protection software configured to prevent installs or data writes to your devices, we recommend that you update to the most current version of that software, if possible. In some cases, you may need to configure an exception for the OfficeClickToRun.exe process in order for the install to complete successfully.
Sample configuration.xml files
For more information about settings available in the configuration.xml file, see Configuration options for the Office Deployment Tool.
Installing and updating Microsoft 365 Apps for enterprise from the Office CDN
Here is a sample configuration.xml file to use with the Office Deployment Tool to install Microsoft 365 Apps for enterprise on Current Channel from the Office CDN. Microsoft 365 Apps for enterprise will also be automatically updated directly from the Office CDN.
Installing and updating Microsoft 365 Apps for enterprise from a shared folder on the local network
Here is a sample configuration.xml file to use with the Office Deployment Tool to install Microsoft 365 Apps for enterprise on Semi-Annual Enterprise Channel from a shared folder on your local network. Updates to Microsoft 365 Apps for enterprise will also come from a shared folder on your local network.
Note
To remove the administrative burden of managing shared folders for updates, we recommend that you configure Microsoft 365 Apps for enterprise to get updates directly from the Office CDN on the internet if possible. If using the Office CDN isn't an option, our next recommendation would be to use Configuration Manager to manage updates.
Configure whether to send telemetry data to Microsoft
Office apps send telemetry data to Microsoft on a regular basis to help Microsoft understand how to improve the product. In highly regulated environments, you may choose to prevent telemetry data from being sent to Microsoft.
No additional configuration is needed to prevent Microsoft 365 Apps for enterprise or Office apps on Android from sending telemetry data to Microsoft. In both cases, the apps can recognize that they are in a GCC High or DoD environment and will automatically prevent telemetry data from being sent to Microsoft.
For other Office apps, such as Skype for Business client, Office for Mac, and Office apps on iOS, additional configuration is needed to prevent telemetry data from being sent to Microsoft. See the following sections for additional information.
Turn off sending telemetry data to Microsoft from Skype for Business client
To prevent Skype for Business client from sending telemetry data to Microsoft, edit the registry and add the TelemetryTier value to the HKEY_CURRENT_USERSoftwarePoliciesMicrosoftOffice16.0Lync key. The type for TelemetryTier is REG_DWORD, and the value should be set to 0.
For more information, see Skype for Business and Microsoft Teams data collection practices.
Group Policy To Deploy Software To Macs Mac
Turn off sending telemetry data to Microsoft from Office for Mac
Office for Mac sends telemetry information back to Microsoft at regular intervals. Data is uploaded to the 'Nexus' endpoint. https://euintensive789.weebly.com/final-cut-pro-104-dmg-download.html. The telemetry data helps the engineering team assess the health and any unexpected behaviors of each Office app. There are two categories of telemetry:
- Heartbeat contains version and license information. This data is sent immediately upon app launch.
- Usage contains information about how apps are being used and non-fatal errors. This data is sent every 60 minutes.
To prevent Office for Mac from sending telemetry data to Microsoft, you can set the SendAllTelemetryEnabled and SendCriticalTelemetryEnabled preferences to 'FALSE.'
Important
You must be using at least Version 16.11 of Office for Mac.
The preferences are per-application and can be set via macOS Configuration Profiles, or manually from Terminal, as shown in the following example.
Turn off sending telemetry data to Microsoft from Office apps on iOS
To prevent Office apps on iOS from sending telemetry data to Microsoft, set the SendAllTelemetryEnabled and SendCriticalTelemetryEnabled preferences to 'false.' The preferences are per-application and can be set by using Microsoft Intune. For more information, see Add app configuration policies for managed iOS devices.
Important
You must be using at least Version 2.11 of Office on iOS.
For each key and value in the configuration, set the following:
- Configuration key = SendAllTelemetryEnabled
- Value type = Boolean
- Configuration value = false
and
- Configuration key = SendCriticalTelemetryEnabled
- Value type = Boolean
- Configuration value = false
Additional settings to configure
In addition to telemetry data settings, there are some additional settings that you may choose to configure depending on your compliance requirements. Many of these settings are configured by making changes to the registry. To deploy registry changes to multiple computers or users, you can use batch files, login scripts, Group Policy, Configuration Manager, PowerShell, or other scripting and deployment tools.
Ensure modern authentication is enabled
Modern authentication needs to be enabled to be compliant. Modern authentication is enabled by default for Office 365 services and in Microsoft 365 Apps for enterprise. Unless you have intentionally disabled modern authentication, no action is required. For more information, see How modern authentication works for Office 2013 and Office 2016 client apps.
Turn off Windows Error Reporting
To disable Windows Error Reporting (Watson), edit the registry and under the HKEY_CURRENT_USERSoftwareMicrosoftWindowsWindows Error Reporting key, set the Disabled value to 1. The type for the Disabled value is REG_DWORD.
Configure Outlook behavior on Microsoft 365 Apps for enterprise
The following registry values must be set to correctly configure Outlook behavior on Microsoft 365 Apps for enterprise. The type for these registry values is REG_DWORD and the values should be set to 1.
Registry location: HKEY_CURRENT_USERSoftwareMicrosoftOffice16.0OutlookAutoDiscoverEnableOffice365ConfigService
Description: This is needed so that the correct mailbox settings may be retrieved in this specific environment without calling a worldwide service to retrieve mailbox settings. If you're using Version 1805 or later of Microsoft 365 Apps for enterprise you don't need to set this registry setting.
Description: This is needed so that the correct mailbox settings may be retrieved in this specific environment without calling a worldwide service to retrieve mailbox settings. If you're using Version 1805 or later of Microsoft 365 Apps for enterprise you don't need to set this registry setting.
Registry location: HKEY_CURRENT_USERSoftwareMicrosoftOffice16.0OutlookSetupDisableAccountSettingsDetectionService
Description: This disables calling a worldwide service that assists in getting account information for POP, IMAP, and other protocols based on the email address. Because this service will be disabled by this key, personal accounts will need to be set up manually.
Description: This disables calling a worldwide service that assists in getting account information for POP, IMAP, and other protocols based on the email address. Because this service will be disabled by this key, personal accounts will need to be set up manually.
Registry location: HKEY_CURRENT_USERSoftwareMicrosoftOffice16.0OutlookOptionsGeneralDisablePreviewPlace
Description: This disables the Coming Soon feature which provides users with information about upcoming features and lets users try those features and provide feedback. Coming Soon is available in Version 1806 or later of Microsoft 365 Apps for enterprise.
Description: This disables the Coming Soon feature which provides users with information about upcoming features and lets users try those features and provide feedback. Coming Soon is available in Version 1806 or later of Microsoft 365 Apps for enterprise.
The following registry values are optional. The type for these registry values is REG_DWORD and the values should be set to 1.
Registry location: HKEY_CURRENT_USERSoftwareMicrosoftOffice16.0OutlookSetupDisableGuessSmart
Description: This disables attempts at setting up IMAP, POP accounts through various known ports.
Description: This disables attempts at setting up IMAP, POP accounts through various known ports.
Registry location: HKEY_CURRENT_USERSoftwareMicrosoftOffice16.0OutlookOptionsGeneralDisableOutlookMobileHyperlink
Description: This suppresses the option of configuring Outlook on a mobile device following a successfully configured account in Outlook Desktop.
Description: This suppresses the option of configuring Outlook on a mobile device following a successfully configured account in Outlook Desktop.
Also, if Office Add-ins are built and used in non-Outlook apps, those applications must know where the user's mailbox is configured. Microsoft will only perform Step 6 and Step 7 of the AutoDiscover process. This means you must have a URL that exists in one of these locations:
https://<contoso.com>.autodiscover/autodiscover.xml
or https://autodiscover.<contoso.com>/autodiscover/autodiscover.xml
. Then, that should redirect to https://autodiscover-s-dod.office365.us/autodiscover/autodiscover.xml
. This process will be automatic in future versions.Special considerations
Due diligence was done to review cloud services connected to features in Microsoft 365 Apps for enterprise. We expect, and have found, that such processes are not failure proof so we have created the following table to capture any edge cases that were not initially captured prior to initial release. We will use this table so we can communicate the finding, any potential risk and the mitigation of that increase in scope. Services in this table will be appropriately turned off within 30 days.
Application | Feature | Recommendation |
---|---|---|
Excel | Maps | This feature has been disabled, as of these releases: - Version 1804 (Build 9226.2126) of Current Channel - Version 1803 (Build 9126.2191) of Semi-Annual Enterprise Channel (Preview) - Version 1803 (Build 9126.2259) of Semi-Annual Enterprise Channel If you're using an earlier version of Excel, don't use this feature. |
Reference information
Office Content Delivery Network (CDN)
The software to install and update Microsoft 365 Apps for enterprise is available on the Office Content Delivery Network (CDN) on the internet. The Click-to-Run service, which manages installations and updates of Microsoft 365 Apps for enterprise, makes calls to the Office CDN, which is hosted by Akamai.
Office 365 has a Memorandum of Understanding with Akamai as part of the Office 365 accreditation package and Akami has a FedRAMP moderate accreditation. For availability, the Click-to-Run service can failover to a world-wide instance of Azure Front Door, which also has a FedRAMP moderate accreditation.
Device Management Service
For installations of Microsoft 365 Apps for enterprise that are configured to get updates automatically from the Office CDN, Microsoft uses the Device Management Service (DMS) to apply release configuration to individual devices based on their specific configuration. For example, the operating system version that Office is installed on, whether the 32-bit or 64-bit version of Office is installed, and which language of Office is installed.
Group Policy To Deploy Software To Macs Download
The Click-to-Run service contacts DMS to check for updates and will get a JSON response letting it know if a new build is available to download. None of the data passed by the Click-to-Run service is stored by the DMS service. The data is merely used as filtering criteria to determine what build information should be provided to the Click-to-Run for updating Microsoft 365 Apps for enterprise.
The DMS service doesn't process, store or transmit any personally identifiable information or customer content.
Related topics
For more information about the GCC High and DoD environments provided by Microsoft, see the following service descriptions:
Group Policy To Deploy Software To Macs Computer
For general deployment guidance about Microsoft 365 Apps for enterprise, see the following articles:
For networking information, see the following articles: