Microsoft Office Standalone Mac

Posted on 01.04.2020admin

Microsoft is aggressively pushing customers to Office 365 subscriptions by changing its support requirements in October 2020.

Microsoft Office Standalone Apps
Microsoft Office Standalone Machine
Ms Office Mac Standalone
Microsoft Office Mac Standalone
Babel Standalone
Chrome Browser Download

Choose Office for your Mac and PC Create your best work with Office 365, and get 1 TB of OneDrive cloud storage for your photos and files. The Office experience you know and love, built for your Mac, PC, iOS and Android devices. Get the latest version of Microsoft Office products for your home or business with Office 2019 and Office 365. Fully-installed versions of Word, Excel, PowerPoint, OneNote for Windows or Mac. Devices per license 3. Licensed for commercial use. Starting with Version 16.21, Microsoft Teams will be installed by default for new installations if you're using the Office suite install package. For more information, see Microsoft Teams installations on a Mac.; For security reason, Microsoft has deprecated the use of SHA-1. 2020-4-1 Microsoft Mac Downloads Page Last Updated: April 1, 2020 @ 2:30pm Pacific Time All links on this page point to Microsoft's official download on its Content Delivery Network (CDN). Use the Office offline installer to install Office 2016 or Office 2013 if you don't have an active Internet connection or you're having problems with slow speed or unreliable connections. Uninstall Office for Mac. These products are usually associated with a personal Microsoft account.

The future of Microsoft Office is subscriptions. That sums up what the company confirmed recently in a blog post notifying users about its plans to wind down support for standalone versions of Office aka perpetual licenses; which want to connect to its Office 365 cloud services. That means versions such as Office 2010, 2013 and 2016 will no longer be able to access O365 cloud services such as Exchange Online, Sharepoint Online, OneDrive for Business or Skype for Business by October 2020.

The company is not ending development of perpetual versions of the suite, but users will need to move to the latest versions in order to access all of Microsoft’s O365 Cloud services. For example, Office 2016 which was launched in September 2015 will have its mainstream support end in 2020. So, if you don’t cut over to a Microsoft Office subscription by then, it will no longer be supported to connect to Microsoft’s cloud services.

Microsoft Winding Down Support for Perpetual Versions of Office

One of the key benefits of Office 365 versus Office 2016 is the ongoing delivery of new features and functionality. Office 2016 Professional Plus has pretty much stood still since its 2015 release, receiving only security updates. Office 365, on the other hand, has received numerous improvements and features such as improved collaboration, business intelligence enhancements in Excel and Motion Path in PowerPoint. For many users, the standalone suite remains attractive, especially for organizations that need control over access to features in the suite. Here is what Microsoft’s Ron Markezich had to say about the changes ahead.

When customers connect to Office 365 with a legacy version of Office, they’re not enjoying all that the service has to offer. The IT benefits—particularly security—are cut short. And the end user experience in the apps is limited to the features shipped at a point in time. To ensure that customers are getting the most out of their Office 365 subscription, we are updating our system requirements.

Office 365 ProPlus or Office perpetual in mainstream support required to connect to Office 365 services. Starting October 13, 2020, Office 365 ProPlus or Office perpetual in mainstream support will be required to connect to Office 365 services. Office 365 ProPlus will deliver the best experience, but for customers who aren’t ready to move to the cloud by 2020, we will also support connections from Office perpetual in mainstream support.
Applies to Office 365 commercial services only. This update does not change our system requirements or support policies for the Office perpetual clients, Office perpetual clients connecting to on-premises servers, or any consumer services.
More than three years’ notice. We’re providing more than three years’ notice to give IT time to plan and budget for this change. Until this new requirement goes into effect in 2020, Office 2010, Office 2013 and Office 2016 perpetual clients will still be able to connect to Office 365 services. Source

Users can read further details about the changes at the company’s Tech Community website. Microsoft is slowly nudging users to move to Office 365, which actually offers greater value in the long run by being cheaper up front, plus it’s continually updated with new features and flexible deployment options. Three years is ample notice, especially for versions such as Office 2010, which would have been expected to stop receiving support by 2020.

The dream of Office as a service goes back as far as Office 2003 when Microsoft had originally planned to offer its suite as a subscription, but the market wasn’t ready. Office 365, first launched in 2011 has evolved over the years to become a consistent revenue generator for the software firm. The rest of the industry has followed suit, brands such as AutoDesk, Adobe, and Intuit have also moved their business models to subscriptions.

-->

Microsoft Teams has clients available for desktop (Windows, Mac, and Linux), web, and mobile (Android and iOS). These clients all require an active internet connection and do not support an offline mode.

Note

Effective November 29, 2018, you'll no longer be able to use the Microsoft Teams for Windows 10 S (Preview) app, available from the Microsoft Store. Instead, you can now download and install the Teams desktop client on devices running Windows 10 S mode. To download the desktop client, go to https://teams.microsoft.com/downloads. MSI builds of the Teams desktop client are not yet available for devices running Windows 10 S mode.

For more information about Windows 10 S mode, see Introducing Windows 10 in S mode.

Desktop client

Tip

Watch the following session to learn about the benefits of the Windows Desktop Client, how to plan for it, and how to deploy it: Teams Windows Desktop Client

The Microsoft Teams desktop client is a standalone application and is also available in Office 365 ProPlus. Teams is available for 32-bit and 64-bit versions of Windows (8.1 or later) and Windows Server (2012 R2 or later), as well as for macOS (10.10 or later) and Linux (in .deb and .rpm formats). On Windows, Teams requires .NET Framework 4.5 or later; the Teams installer will offer to install it for you if you don't have it. On Linux, package managers such as apt and yum will try to install any requirements for you. However, if they don't then you will need to install any reported requirements before installing Teams on Linux.

The desktop clients provide real-time communications support (audio, video, and content sharing) for team meetings, group calling, and private one-on-one calls.

Desktop clients can be downloaded and installed by end users directly from https://teams.microsoft.com/downloads if they have the appropriate local permissions (admin rights are not required to install the Teams client on a PC but are required on a Mac).

IT admins can choose their preferred method to distribute the installation files to computers in their organization. Some examples include Microsoft Endpoint Configuration Manager (Windows) or Jamf Pro (macOS). To get the MSI package for Windows distribution, see Install Microsoft Teams using MSI.

Note

Distribution of the client via these mechanisms is only for the initial installation of Microsoft Team clients and not for future updates.

Windows

The Microsoft Teams installation for Windows provides downloadable installers in 32-bit and 64-bit architecture.

Note

The architecture (32-bit vs. 64-bit) of Microsoft Teams is agnostic to the architecture of Windows and Office that is installed.

The Windows client is deployed to the AppData folder located in the user’s profile. Deploying to the user’s local profile allows the client to be installed without requiring elevated rights. The Windows client leverages the following locations:

%LocalAppData%MicrosoftTeams
%LocalAppData%MicrosoftTeamsMeetingAddin
%AppData%MicrosoftTeams
%LocalAppData%SquirrelTemp

When users initiate a call using the Microsoft Teams client for the first time, they might notice a warning with the Windows firewall settings that asks for users to allow communication. Users might be instructed to ignore this message because the call will work, even when the warning is dismissed.

Use Microsoft Word for the best word processing and document creation. Find out how document collaboration and editing tools can help polish your Word docs. Microsoft word backup mac.

Note

Windows Firewall configuration will be altered even when the prompt is dismissed by selecting “Cancel”. Two inbound rules for teams.exe will be created with Block action for both TCP and UDP protocols.

Mac

Mac users can install Teams by using a PKG installation file for macOS computers. Administrative access is required to install the Mac client. The macOS client is installed to the /Applications folder.

Install Teams by using the PKG file

From the Teams download page, under Mac, click Download.
Double click the PKG file.
Follow the installation wizard to complete the installation.
Teams will be installed to /Applications folder. It is a machine-wide installation.

Note

During the installation, the PKG will prompt for admin credentials. The user needs to enter the admin credentials, regardless of whether or not the user is an admin.

If a user currently has a DMG installation of Teams and wants to replace it with the PKG installation, the user should:

Exit the Teams app.
Uninstall the Teams app.
Install the PKG file.

Microsoft Office Standalone Apps

IT admins can use managed deployment of Teams to distribute the installation files to all Macs in their organization, such as Jamf Pro.

Note

If you experience issues installing the PKG, let us know. In the Feedback section at the end of this article, click Product feedback.

Linux

Users will be able to install native Linux packages in .deb and .rpm formats.Installing the DEB or RPM package will automatically install the package repository

DEB https://packages.microsoft.com/repos/ms-teams stable main
RPM https://packages.microsoft.com/yumrepos/ms-teams

The signing key to enable auto-updating using the system's package manager is installed automatically. However, it can also be found at: (https://packages.microsoft.com/keys/microsoft.asc). Microsoft Teams ships monthly and if the repository was installed correctly, then your system package manager should handle auto-updating in the same way as other packages on the system.

Note

If you find a bug, submit it using Report a Problem from within the client. For known issues, see Known Issues.For Teams for Linux support you can use the Linux forum support channel on Microsoft Q&A. Be sure to use the teams-linux tag when posting questions.

Install Teams using DEB package

Download the package from https://aka.ms/getteams.
Install using one of the following:
- Open the relevant package management tool and go through the self-guided Linux app installation process.
- Or if you love Terminal, type: sudo apt install **teams download file**

You can launch Teams via Activities or via Terminal by typing Teams.

Install Teams using RPM package

Download the package from https://aka.ms/getteams.
Install using one of the following:
- Open the relevant package management tool and go through the self-guided Linux app installation process.
- Or if you love Terminal, type: sudo yum install **teams download file**

You can launch Teams via Activities or via Terminal by typing Teams.

Install manually from the command line

Install manually on Debian and Ubuntu distributions:

Microsoft Office Standalone Machine

Install manually on RHEL, Fedora and CentOS based distributions:

Ms Office Mac Standalone

Alternatively, to use yum instead of dnf:

Install manually on openSUSE based distributions:

Web client

The web client (https://teams.microsoft.com) is a full, functional client that can be used from a variety of browsers. The web client supports Calling and Meetings by using webRTC, so there is no plug-in or download required to run Teams in a web browser. The browser must be configured to allow third-party cookies.

Teams fully supports the following Internet browsers, with noted exceptions for calling and meetings.

Browser	Calling - audio, video, and sharing	Meetings - audio, video, and sharing¹²
Internet Explorer 11	Not supported	Meetings are supported only if the meeting includes PSTN coordinates. To attend a meeting on IE11 without PSTN coordinates, users must download the Teams desktop client. Video: Not supported Sharing: Incoming sharing only (no outgoing)
Microsoft Edge, RS2 or later	Fully supported, except no outgoing sharing	Fully supported, except no outgoing sharing
Microsoft Edge (Chromium-based), the latest version plus two previous versions	Fully supported	Fully supported
Google Chrome, the latest version plus two previous versions	Fully supported	Fully supported Sharing is supported without any plug-ins or extensions on Chrome version 72 or later.
Firefox, the latest version plus two previous versions	Not supported	Meetings are supported only if the meeting includes PSTN coordinates. To attend a meeting on Firefox without PSTN coordinates, users must download the Teams desktop client. Video: Not supported Sharing: Incoming sharing only (no outgoing)
Safari 11.1+	Not supported	Meetings are supported only if the meeting includes PSTN coordinates. To attend a meeting on Safari without PSTN coordinates, users must download the Teams desktop client. Video: Not supported Sharing: Incoming sharing only (no outgoing) Safari is enabled on versions higher than 11.1 in preview. While in preview, there are known issues with Safari's Intelligent Tracking Prevention.

Microsoft Office Mac Standalone

¹ To give and take control of shared content during sharing, both parties must be using the Teams desktop client. Control isn't supported when either party is running Teams in a browser. This is due to a technical limitation that we're planning to fix. To learn more, read Allow a participant to give or request control.

Babel Standalone

² Blur my background isn't available when you run Teams in a browser. This feature is only available in the Teams desktop client.

Note

As long as an operating system can run the supported browser, Teams is supported. For example, running Firefox on the Linux operating system is an option for using Teams.

The web client performs browser version detection upon connecting to https://teams.microsoft.com. If an unsupported browser version is detected, it will block access to the web interface and recommend that the user download the desktop client or mobile app.

Mobile clients

The Microsoft Teams mobile apps are available for Android and iOS, and are geared for on-the-go users participating in chat-based conversations and allow peer-to-peer audio calls. For mobile apps, go to the relevant mobile stores Google Play and the Apple App Store. The Windows Phone App was retired July 20, 2018 and may no longer work.

In China, here's how to get Teams for Android.

Supported mobile platforms for Microsoft Teams mobile apps are the following:

Android: Support is limited to the last four major versions of Android. When a new major version of Android is released, the new version and the previous three versions are officially supported.
iOS: Support is limited to the two most recent major versions of iOS. When a new major version of iOS is released, the new version of iOS and the previous version are officially supported.

Note

The mobile version must be available to the public in order for Teams to work as expected.

Mobile apps are distributed and updated through the respective mobile platform’s app store only. Distribution of the mobile apps via MDM or side-loading is not supported by Microsoft. Once the mobile app has been installed on a supported mobile platform, the Teams Mobile App itself will be supported provided the version is within three months of the current release.

Decision Point	Are there any restrictions preventing users from installing the appropriate Microsoft Teams client on their devices?
Next Steps	If your organization restricts software installation, make sure that process is compatible with Microsoft Teams. Note: Admin rights are not required for PC client installation but are required for installation on a Mac.

Client update management

Clients are currently updated automatically by the Microsoft Teams service with no IT administrator intervention required. If an update is available, the client will automatically download the update and when the app has idled for a period of time, the update process will begin. Microsoft windows vs mac os vs linux.

Client-side configurations

Currently, there are no supported options available to configure the client either through the tenant admin, PowerShell, Group Policy Objects or the registry.

Notification settings

There are currently no options available for IT administrators to configure client-side notification settings. All notification options are set by the user. The figure below outlines the default client settings.

Sample PowerShell Script

Chrome Browser Download

This sample script, which needs to run on client computers in the context of an elevated administrator account, will create a new inbound firewall rule for each user folder found in c:users. When Teams finds this rule, it will prevent the Teams application from prompting users to create firewall rules when the users make their first call from Teams.