- Submitting an App to the Mac App Store. Packaging an app for the Mac App Store is similar to packaging for regular distribution up until the step of signing the app. Signing the app for the Mac App Store requires a few more steps, and a different kind of certificate. You will need to create an application ID and then obtain a distribution.
- Here’s how to submit your app to the Apple App Store: Create an iOS distribution provisioning profile and distribution certificate. Create an App Store Connect record for your app. Archive and upload your app using Xcode. Configure your app’s metadata and further details in its App Store Connect record. Submit your app for review.
- Add in-app updates to your app. Follow the Get started section if you haven't configured the SDK in your application. Add the App Center Distribute module. The App Center SDK is designed with a modular approach – you only need to integrate the modules of the services that you're interested in.
- Mac App Distribution Guide Pdf
- Mac App Distribution Guide Download
- Mac App Distribution Guide App
- Mac App Distribution Guide Template
Some MDMs may support managed distribution and/or redeemable codes. Contact your MDM provider for more information on the requirements. While in-app purchases aren't supported as standalone content that can be bought and distributed with Apps and Books, end users can make and restore in-app purchases from within Apps and Books-assigned apps, as long as those apps aren't device-assigned.
For iOS Apps
There are two cases which you want to distribute your applications outside the App Store:
- Testing Purpose: Before releasing your apps, you would want to test them as much as you can. Thus, you would want to distribute your apps to users (testers) by various ways besides the App Store.
- In-house Applications: The applications are made for internal uses (in a company or organization) only.
For in-house distribution, you will need to have an Apple Developer Enterprise Program account.
The differences between Apple Developer and Apple Developer Enterprise programs regarding apps distribution:
Apple Developer Program | Apple Developer Enterprise Program | |
---|---|---|
Beta OS Releases | Yes | Yes |
Ad Hoc Distribution | Yes | Yes |
App Store Distribution | Yes | No |
In-house Distribution | No | Yes |
TestFlight Beta Testing | Yes | No |
Team Management | No | Yes |
App Analytics | Yes | No |
For more information about the differences between the two programs, please refer to Choosing a Membership.
There are two ways to distribute your pre-release apps for testing:
- using App Store Connect: it’s required iOS Developer Account and takes time since it needs approval from Apple Review prior to the distribution.
- using Ad Hoc distribution: it can be done with either iOS Developer and iOS Developer Enterprise accounts. Plus, it doesn’t require the approval from Apple Review.
In-house distribution is to securely distribute your iOS apps to your employees. In other words, you can distribute your app to any company devices. However, if you want someone outside of your company to test your app or restrict distribution to specific devices, you can use Ad Hoc distribution.
Ad Hoc distribution is to distribute your apps using Ad Hoc provisioning profile to registered devices up to
100
.Both types of distribution have the same ways for app installation. The difference is the provisioning profile.
There are several ways you can install your applications outside the App Store as shown in the following sections.
Install using Apple Configurator 2 (Mac Only)
- Install
Apple Configurator 2
on your Mac from the App Store. - Connect your device to your PC.
- Open
Apple Configurator 2
, select your device. If you device doesn’t appear here, please make sure that your device is successfully connected to your Mac. - Click on Add button and select
App
option. - Select Choose from my Mac button and browse the
.ipa
file. Then, the app will be installed on your device.
Install using Xcode
You can install your iOS app (
.ipa
file) via Xcode as follows:- Connect your device to your PC.
- Open Xcode, go to Window → Devices .
- Then, the Devices screen will appear. Choose the device you want to install the app on.
- Drag and drop your
.ipa
file into the Installed Apps as shown below:
Install using iTunes
iTunes 12.7 for Mac was released on Tuesday with a major change in the app. Apple has redesign iTunes so that it focuses on sales of music, movies, TV shows, audiobooks, and podcasts. It no longer has an App Store for buying apps for your iPhone or iPad. Therefore, you can no long install your iOS App (.ipa file) through iTunes any longer.
- Build your application with with debug or ad-hoc build. For moredetails about iOS build process, please refer to Building an iOS App.
- Download the
.ipa
file after the build completes. - Open iTunes, go to
App library
. - Drag and drop the downloaded
.ipa
file into theApp library
. - Connect your device to iTunes and go to your device apps.
- Click Install button of the app and click Sync button. See the example below:
Install using OTA Deployment
OTA (Over-The-Air) Deployment enables you to install your built apps via HTTPS.
- Build your application with either debug, ad-hoc or in-house build. For moredetails about iOS build process, please refer to Building an iOS App.
- Download the
.ipa
file after the build completes. - Upload the
.ipa
file to the site you want. - Create a
.plist
file for this built application. The.plist
file should look like this:While creating.plist
file, please pay attention to these points:.plist
file must be accessed via https protocol.- update bundle-identifier with the App ID.
- specify correct path to the
.ipa
file.
- Upload the
.plist
file to the site you want. Make sure this filemust be accessed via HTTPS protocol. - Create a webpage embedded the link to the uploaded
.plist
fileusing specialitms-services://
protocol. See blow example: - After you get the link, use your device to access the link. Then,you will be prompted to install the application. See below example:
For Android Apps
There are two cases which you want to distribute your applicationsoutside the offical markets such as Google Play Store, Amazon AppStoreand so on:
- Testing Purpose: Before releasing your apps, you would want to testthem as much as you can. Thus, you would want to distribute yourapps to users (testers) by various ways besides the officialmarkets.
- Personal/Internal Purpose: The applications are made for your ownpersonal uses or just for internal uses.
Install using ADB command
ADB (Android Debug Bridge) is a tool enabling you to use variousterminal commands to your phone.
Prerequisite:
- install Android SDK on your computer
- locate the ADB path after Android SDK installation
- enable USB Debugging and allow installation of apps from sourcesother than the Play Store on your device.
In order to install your built app via ADB command:
- Build your application with debug build. For more details aboutAndroid build process, please refer to Building for Android.
- Download the
.apk
file after the build completes. - Plug your device via USB to your computer.
- Run below command on your computer in command window. Make sure touse the correct path to your
.apk
file.
Install using Direct Link
This is simply an installation through direct link to your
.apk
file:- Build your application with debug build. For more details aboutAndroid build process, please refer to Building for Android.
- Download the
.apk
file after the build completes. - Upload the downloaded file to any sites you want.
- Go the link of the uploaded file from your device. Then, you will beprompted to install the applicaiton.Please make sure make these settings on your device beforehand:
- enable USB Debugging.
- allow installation of apps from sources other than the Play Store.
See Also:
-->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
For details about each clients' capabilities on different platforms, see Teams features by platform.
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 Microsoft 365 Apps for enterprise. Teams is available for 32-bit and 64-bit versions of Windows (8.1 or later), ARM64 for Windows 10 on ARM, and Windows Server (2012 R2 or later), as well as for macOS 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).
Note
For more details about installing Teams on a Chromebook, please see How to install and run Microsoft Office on a Chromebook.
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.
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 Allow action for both TCP and UDP protocols.
If you want to prevent Teams from prompting users to create firewall rules when the users make their first call from Teams, use the Sample PowerShell script - inbound firewall rule below.
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.
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
Mac App Distribution Guide Pdf
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 Support Teams in your organization.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:
Install manually on RHEL, Fedora and CentOS based distributions:
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. This table applies to operating systems running on desktop computers.
Browser | Calling - audio, video, and sharing | Meetings - audio, video, and sharing123 |
---|---|---|
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 365 apps and services will not support Internet Explorer 11 starting August 17, 2021 (Microsoft Teams will not support Internet Explorer 11 earlier, starting November 30, 2020). Learn more. Please note that Internet Explorer 11 will remain a supported browser. Internet Explorer 11 is a component of the Windows operating system and follows the Lifecycle Policy for the product on which it is installed. |
Microsoft Edge, RS2 or later | Fully supported, except no outgoing sharing4 | 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. |
Safari 13.1+ | 1:1 calls not supported. Group calls supported with full audio support. Video: Incoming only Sharing: Incoming sharing only (no outgoing) | Meetings are supported with full audio support. Video: Incoming only Sharing: Incoming sharing only (no outgoing). Note that only a user's entire display can be shared; sharing specific windows within a display is not available. |
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 versions before 13 | 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. |
1 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.
2 Blur my background isn't available when you run Teams in a browser. This feature is only available in the Teams desktop client.
3 Teams meetings on browsers are limited to a single incoming video feed of active speaker.
4 Edge RS2 or later doesn't support sending real-time audio and video traffic through HTTP proxies.
Note
As long as an operating system can run the supported browser, Teams is supported on desktop computers. For example, running Firefox on the Linux operating system is an option for using Teams.
For mobile operating systems, we recommend that you run the Teams app, available from the Android and iOS stores. Running Teams in a mobile operating system is supported, but many features are unavailable.
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.
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. Mac os how to chanege default app.
Mac App Distribution Guide Download
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.
Mac App Distribution Guide App
Sample PowerShell script - inbound firewall rule
Mac App Distribution Guide Template
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.