Download and install Office 2016 for Mac. Sign in with your work account here. On the Office page, under Install Office 2016 for Mac, select Install to begin downloading the installer package. Once the download has completed, open Finder, go to Downloads, and double-click MicrosoftOffice2016Installer.pkg. (The name might vary slightly.). If you're the Microsoft 365 admin of an Office for business plan, users in your organization can only install Office using the steps in this topic as long as your plan includes the desktop version of Office, and you've assigned the user a license and given them permission to install Office (Manage software download settings in Microsoft 365).

Use Office 365 Pro Plus for free on up to five desktop computers (Mac or Windows) and up to five mobile devices. Save up to 5,000 GB of file storage.

Here I’m sharing my experience of activate Office 365 online and downloading offline installers for Windows ISO, and macOS PKG. Difference between office 365 and Office 2019 The main difference between Office 365 and Office is the pricing, the availability of cloud applications like OneDrive and premium, etc.


IMPORTANT: Office 365 Pro Plus and OneDrive for Business file storage is available to students only while enrolled at Marquette University. Students who leave prior to graduating may have their accounts disabled immediately, which includes access to Office 365 Pro Plus and OneDrive for Business. New graduates retain access to Office 365 Pro Plus and OneDrive for Business for approximately one year after the term they graduate. Be sure to transfer all your OneDrive for Business file storage before you leave Marquette.


IMPORTANT: Office 365 Pro Plus and OneDrive for Business file storage is available to faculty and staff only while employed at Marquette University.

Applications within Office 365 Pro Plus include:

  • Windows: Word, Excel, PowerPoint, OneNote, Access, Publisher, Outlook, Teams, OneDrive for Business.
    Microsoft recommends installing the 64-bit version of Office 365 Pro Plus, which is the default installation. Learn more.
  • Mac: Word, Excel, PowerPoint, Outlook and OneNote. (Microsoft Teams is free, separate download.)
  • iPad:Word, Excel, PowerPoint, Microsoft Teams and OneNote are free, separate downloads.
  • iPhone/iPod Touch, Windows Phone and Android phones: Apps for Word, Excel, PowerPoint, Teams and OneNote Mobile are free, separate downloads. See the Apple App Store or Google Play Store.

  1. CRITICAL: If you are installing Office 365 Pro Plus on a computer with an existing version of Office, that version of Office must be uninstalled before installing Office 365 Pro Plus.
    TO AVOID COMPUTER PROBLEMS, use these resource links to uninstall Microsoft Office:

  2. Go to
  3. To log in, use your Marquette email address (in the form of [email protected]) and your Marquette password (same one used for eMarq, CheckMarq and D2L).
  4. Click or tap Install Office then >Office 365 Apps.
  5. This starts to download a Setup file.
  6. Follow the installer prompts to finish Office 365 Pro Plus installation.


A package file, Microsoft_Office_16.35.20030802_BusinessPro_Installer.pkg, will download. When complete, open Microsoft_Office_16.35.20030802_BusinessPro_Installer.pkg. A window appears with Microsoft Office installer. Double-click Microsoft Office installer to begin installation.
If you receive an error message stating Office 'cannot be installed because it was not downloaded from the Mac App store,' follow these instructions. Go to Apple menu > System Preferences > Security & Privacy > General tab. Under the header 'Allow applications downloaded from,' select

Office 365 Pkg Login

Mac App Store and identified developers. Close the preferences window. Relaunch the Office installer. (See more detailed instructions from Apple.)
MAC USERS: After installation, be sure to choose Sign in to an existing Office 365 subscription.
MAC USERS, PLEASE NOTE: After selecting the subscription option, you must enter your Marquette email address (not your Marquette username). You will need to sign-in again using your Marquette email address (not your Marquette username) and Marquette password.
  1. From your mobile device, launch a web browser.
  2. Go to
  3. From that Microsoft web page, select your device.
  4. A web page for your device appears. Select the download or get button.
  5. Download and install the app on your device, as you would for any other app. This is a free installation.
  6. Launch the app.
  7. Advance past introductory screens to get to sign-in.
  8. You are prompted to sign in. For email address, be sure to use your Marquette email address, following the format of [email protected]. Click Next.
  9. You will see another sign-in prompt with your Marquette email address filled in. Enter your Marquette password (same one used for eMarq, CheckMarq and D2L). Tap the 'Sign in' button.
  10. Microsoft will confirm your sign-in. If successful, you will be prompted to continue and use the app.

For questions about Office 365 Pro Plus, please contact the IT Services Help Desk at (414) 288-7799 or [email protected]


Being able to connect a Microsoft 365 group to an existing SharePoint site is important if you want to modernize that site. After your site is connected to a Microsoft 365 group, it can benefit from all other group-connected services such as Microsoft Teams and Planner. This connection also brings your classic site a step closer to being like the current modern team site, which by default is connected to a Microsoft 365 group.

You can connect your site to a new Microsoft 365 group from the user interface site-by-site, which might be good for smaller environments. However, larger customers often want to offer a consistent experience to their users, and therefore want to perform a bulk operation of their sites.

In this article, you'll learn how to prepare for such a bulk operation for associating sites to new Microsoft 365 groups and how to actually make it happen.



  • It is not supported to connect a Communication site to Microsoft 365 group.
  • You cannot group connect the root site collection in your tenant.


Modernization tooling and all other PnP components are open-source tools backed by an active community providing support for them. There is no SLA for open-source tool support from official Microsoft support channels.

What connecting to a new Microsoft 365 group does to your site

When you connect your site to a new Microsoft 365 group, a number of things happen:

  • A new Microsoft 365 group is created, and that group is connected to your site collection
  • A new modern home page is created on your site and set as the site's home page
  • The group's Owners are now the site collection administrators
  • The group's Owners are added to your site's Owners group
  • The group's Members are added to your site's Members group

After your site is connected to a Microsoft 365 group, it behaves like a modern group-connected team site, so granting people permission to the connected Microsoft 365 group now also grants them access to the SharePoint site, a Microsoft Team can be created on top of the site, Planner can be integrated, and so on.

Connect a Microsoft 365 group using the SharePoint user interface


One approach to connect a Microsoft 365 group to your site is to use the option available in the user interface. By selecting the gear icon in the navigation bar, you can select the Connect to new Microsoft 365 group option, which launches a wizard that walks you through the group-connection process as shown in the following screenshots.

Office 365 Package Plan

Office 365 pkg downloadDownload

Office 365 Outlook Login

Site actions menu (gear icon)


Programmatically connect a Microsoft 365 group

To programmatically connect a Microsoft 365 group, we recommend that you follow a three-step process:

  • Learn
  • Analyze
  • Modernize

Step 1: Learn what group-connection does to your site

Getting familiar with what group-connection does to your site is important, and therefore we recommend that you do a manual group-connection for some test sites by using the user interface option. An important aspect to evaluate is whether you want to keep the newly created modern home page. As part of the modernization script, you'll be able to create a tailored home page, but if the default one serves your needs, that's the preferred option.

Step 2: Analyze your sites

The user interface option shown in the previous section is not suitable if you want to group-connect hundreds of site collections. At that point, using an API to programmatically do this makes a lot of sense. But before doing that, it's best to verify which sites are ready to be group-connected because not all sites are suitable for this.

To help you understand which sites are ready to be group-connected, you can use the SharePoint Modernization Scanner to analyze your environment. This link contains all the details needed to run the scanner. After you've run the scanner go the Understand and process the scanner results article to analyze the scan results.

Step 3: Modernize your sites

The bulk group-connect process consists of two steps:

  • Prepare and validate an input file that you'll use to drive the bulk group-connect process.
  • Run the bulk group-connect process.

Create an input file for bulk group-connection and validate it

After running the scanner and processing the results, you have identified which sites are ready to group-connect.The next step is to prepare a CSV file to drive the bulk group-connection process. The CSV file format is simple:

  • URL column contains the URL to the site collection to group-connect.
  • Alias contains the Microsoft 365 group alias that you want to use. Note that this alias cannot contain spaces, and it should not have been used before.
  • IsPublic indicates whether you want the site to be a public or private site.
  • Classification contains the site classification that you want to set to the site after you group-connect. This is needed because after being connected to a group, this classification is maintained at the Microsoft 365 group level.

Following is a short sample:

To help you verify this file before using it, you can use the PowerShell script at the end of this section. This script checks for valid site URLs and aliases. Update this script with your tenant admin center URL and run it. The script asks for the CSV file name and generates a report for you.

Office 365 Pkg

During the validation script execution, the following errors can appear:

AzureAD Naming policy : PrefixSuffix does contain AD attributes that are resolved based on the user running the group-connectionIn Azure AD, you can define a naming policy for Microsoft 365 groups. If this policy contains user Active Directory attributes, this might be an issue because bulk group-connect handles all sites using the current user.
AzureAD Creation policy : adminUPN is not part of group CanCreateGroupsId that controls Microsoft 365 group creationIf Azure AD group creation is restricted to certain accounts and the current account is not among those, the Microsoft 365 group creation fails.
siteUrl : Alias [siteAlias] contains a space, which is not allowedThe alias of a Microsoft 365 group cannot contain a space.
siteUrl : Classification [siteClassification] does not comply with available Azure AD classifications [ClassificationListString]The provided site classification is not defined as one of the allowed site classifications for Microsoft 365 groups.
siteUrl : Alias [siteAlias] is in the Azure AD blocked word list [CustomBlockedWordsListString]If a blocked words list is set up in Azure AD and the provided Microsoft 365 group name uses such a word, this error is generated.
siteUrl : Site is already connected to a groupA site can only be connected to a single Microsoft 365 group, so after a site is connected, it cannot be group-connected anymore.
siteUrl : Alias [siteAlias] is already in useEach Microsoft 365 group needs a unique alias; an error is generated when the proposed alias was already used by another Microsoft 365 group.
siteUrl : Alias [siteAlias] was already marked as approved alias for another site in this fileThe proposed site alias was already defined for another site in earlier input lines of the bulk group-connect CSV file.
siteUrl : Site does not exist or is not available (status = site.Status)The provided site URL does not represent a reachable site collection.


Please update the $tenantAdminUrl variable in the following script to contain your tenant admin center URL (for example,

During script execution, a log file is generated, combined with an error file that contains a subset of the log file (only the errors).

Run the bulk group-connect process

Now that we have an input file that's defining the sites that need to be group-connected, we can finally make it happen. The following PowerShell script is a sample script that you can tweak to your needs because you might want more or fewer things as part of the group-connection.

The shared sample version of the script implements the following steps:

  • Adds current tenant admin as site admin when needed; group-connection requires a user account (so no app-only).
  • Verifies site template / publishing feature use and prevents group-connection; aligns with the logic in the scanner.
  • Ensures that no modern blocking features are enabled, and if so, fixes them.
  • Ensures that the modern page feature is enabled.
  • Optional: Deploys applications (for example, Application Customizer).
  • Optional: Adds your own modern home page.
  • Calls the group-connect API.
  • Defines site admins and site owners as group owners.
  • Defines site members as group members.
  • Removes added tenant admin and site owners from SharePoint admins.
  • Removes added tenant admin from the Microsoft 365 group.

Running the following PowerShell script requires that you update the tenant admin center URL and at run time provide credentials and the CSV input file.


This is a sample script that you need to address to your needs by updating/dropping the optional parts or by adding additional modernization tasks (such as setting a SharePoint site theme). Please update the $tenantAdminUrl variable in the script to contain your tenant admin center URL (for example,

During script execution, a log file is generated, combined with an error file that contains a subset of the log file (only the errors).

See also