Uninstall Office for Mac

Uninstall Office for Mac

according to https://support.office.com/en-US/article/uninstall-office-for-mac-eefa1199-5b58-43af-8a3d-b73dc1a8cae3

Excel for Office 365 for Mac Word for Office 365 for Mac More...

You can easily uninstall Office for Mac apps such as Word, Excel, PowerPoint, OneNote, and Outlook using these instructions. You must be signed in as an administrator on the Mac or provide an administrator name and password to complete these steps.

Newer versionsOffice for Mac 2011

You must be signed in as an administrator on the Mac or provide an administrator name and password to complete these steps.

Remove Office for Mac applications

1. Open Finder > Applications.
2. Command  +click to select all of the Office for Mac applications.
3. Ctrl+click an application you selected and click Move to Trash.
   

Remove files from your user Library folder

1. In Finder, press  +Shift+g.
2. In the window that opens, enter ~/Library and then click Go.
3. Open the Containers folder and ctrl+click each of these folders and Move to Trash. Note that some of these folders may not be present.
   • com.microsoft.errorreporting
   • com.microsoft.Excel
   • com.microsoft.netlib.shipassertprocess
   • com.microsoft.Office365ServiceV2
   • com.microsoft.Outlook
   • com.microsoft.Powerpoint
   • com.microsoft.RMS-XPCService
   • com.microsoft.Word
   • com.microsoft.onenote.mac
4. Warning: Outlook data will be removed when you move the three folders listed in this step to Trash. You should back up these folders before you delete them.
   Click the back arrow to go back to the Library folder and open Group Containers. Ctrl+click each of these folders if present, and Move to Trash.
   • UBF8T346G9.ms
   • UBF8T346G9.Office
   • UBF8T346G9.OfficeOsfWebHost

Remove from Dock and restart

1. If you put any of the Office applications in your Dock, go to each one and ctrl + click > Options > Remove from Dock.
   
2. Restart your Mac to complete the uninstall.

Office 365 – Nonprofit Cloud Subscription Canada

As per:
https://www.techsoupcanada.ca/en/microsoft-cloud/product/office-365-%E2%80%93-nonprofit-cloud-subscription

Description:

Eligible nonprofits and charities can receive discounted subscriptions to Office 365 through TechSoup Canada. 

Click GET THIS OFFER to get started.

You don't need to add anything to your TechSoup Canada cart or go through the TechSoup Canada checkout process.

What Is Office 365?

Office 365 provides you and your staff with

• The latest Office desktop applications for PC and Mac and apps for mobile devices (certain subscriptions only)
• Cloud-based access to Office applications
• Hosted email and calendars with Exchange Online
• Instant messaging and web and video conferencing through Skype for Business
• Access to your documents from anywhere with OneDrive for Business
• More, depending on the subscription plan

See the Subscription Options tab for prices and subscription information.

How Can My Organization Benefit from Using Office 365?

Learn about Office Web Apps, hosted email, document sharing, and other benefits provided by Office 365 in this TechSoup article: What You Need to Know About Microsoft Office 365 Nonprofit.

You can also download a free Office 365 e-book to learn more about how nonprofits can use cloud services.

How Much Does Office 365 Cost?

There are both donated and discounted plans available, depending on your needs. See the Subscription Options tab for prices and subscription information.

What Are the System Requirements for Office 365?

See Microsoft's System requirements for Office page. The requirements are listed under "Office 365 plans for business, education, and government."

Subscription Options

Office 365 Nonprofit Business Essentials free	Most suitable for small and mid-sized nonprofits with up to 300 users that do not need Office desktop applications Provides cloud-based access to Office applications, email, instant messaging, HD video conferencing, and 1 TB personal file storage and sharing Does not include Office desktop applications
Office 365 Nonprofit Business Premium $3.70/user/month	Most suitable for small and mid-sized nonprofits with up to 300 users that need Office desktop applications Office desktop applications for PC and Mac included, with apps for tablets and phones Includes all features of Business Essentials plan plus additional features and services
Office 365 Nonprofit E1 free	Most suitable for small and mid-sized nonprofits with up to 300 users that do not need Office desktop applications Provides cloud-based access to Office applications, email, instant messaging, HD video conferencing, and 1 TB personal file storage and sharing Does not include Office desktop applications
Office 365 Nonprofit E3 $5.60/user/month	Most suitable for large nonprofits with more than 300 users that need Office desktop applications Office desktop applications for PC and Mac included, with apps for tablets and phones Includes all features of E1 plan plus data protection and other services
Office 365 Nonprofit E5 $18.50/user/month	Most suitable for large nonprofits with more than 300 users that need Office desktop applications Office desktop applications for PC and Mac included, with apps for tablets and phones Includes all features of E3 plan plus advanced security and other services

IT Consultant
www.inCOREporation.com

Integrate your on-premises directories with Azure Active Directory

https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnect

Azure AD Connect will integrate your on-premises directories with Azure Active Directory. This allows you to provide a common identity for your users for Office 365, Azure, and SaaS applications integrated with Azure AD. This topic will guide you through the planning, deployment, and operation steps. It is a collection of links to the topics related to this area.

Important

Azure AD Connect is the best way to connect your on-premises directory with Azure AD and Office 365. This is a great time to upgrade to Azure AD Connect from Windows Azure Active Directory Sync (DirSync) or Azure AD Sync as these tools are now deprecated are no longer supported as of April 13, 2017.

Why use Azure AD Connect

Integrating your on-premises directories with Azure AD makes your users more productive by providing a common identity for accessing both cloud and on-premises resources. Users and organizations can take advantage of the following:

• Users can use a single identity to access on-premises applications and cloud services such as Office 365.
• Single tool to provide an easy deployment experience for synchronization and sign-in.
• Provides the newest capabilities for your scenarios. Azure AD Connect replaces older versions of identity integration tools such as DirSync and Azure AD Sync. For more information, see Hybrid Identity directory integration tools comparison.

How Azure AD Connect works

Azure Active Directory Connect is made up of three primary components: the synchronization services, the optional Active Directory Federation Services component, and the monitoring component named Azure AD Connect Health.

• Synchronization - This component is responsible for creating users, groups, and other objects. It is also responsible for making sure identity information for your on-premises users and groups is matching the cloud.
• AD FS - Federation is an optional part of Azure AD Connect and can be used to configure a hybrid environment using an on-premises AD FS infrastructure. This can be used by organizations to address complex deployments, such as domain join SSO, enforcement of AD sign-in policy, and smart card or 3rd party MFA.
• Health Monitoring - Azure AD Connect Health can provide robust monitoring and provide a central location in the Azure portal to view this activity. For additional information, see Azure Active Directory Connect Health.

Install Azure AD Connect

You can find the download for Azure AD Connect on Microsoft Download Center.

Solution	Scenario
Before you start - Hardware and prerequisites	Steps to complete before you start to install Azure AD Connect.
Express settings	If you have a single forest AD then this is the recommended option to use. User sign in with the same password using password synchronization.
Customized settings	Used when you have multiple forests. Supports many on-premises topologies. Customize your sign-in option, such as ADFS for federation or use a 3rd party identity provider. Customize synchronization features, such as filtering and writeback.
Upgrade from DirSync	Used when you have an existing DirSync server already running.
Upgrade from Azure AD Sync or Azure AD Connect	There are several different methods depending on your preference.

After installation you should verify it is working as expected and assign licenses to the users.

Next steps to Install Azure AD Connect

Topic	Link
Download Azure AD Connect	Download Azure AD Connect
Install using Express settings	Express installation of Azure AD Connect
Install using Customized settings	Custom installation of Azure AD Connect
Upgrade from DirSync	Upgrade from Azure AD sync tool (DirSync)
After installation	Verify the installation and assign licenses

Learn more about Install Azure AD Connect

You also want to prepare for operational concerns. You might want to have a stand-by server so you easily can fall over if there is a disaster. If you plan to make frequent configuration changes, you should plan for a staging mode server.

Topic	Link
Supported topologies	Topologies for Azure AD Connect
Design concepts	Azure AD Connect design concepts
Accounts used for installation	More about Azure AD Connect credentials and permissions
Operational planning	Azure AD Connect sync: Operational tasks and considerations
User sign-in options	Azure AD Connect User sign-in options

Configure sync features

Azure AD Connect comes with several features you can optionally turn on or are enabled by default. Some features might sometimes require more configuration in certain scenarios and topologies.

Filtering is used when you want to limit which objects are synchronized to Azure AD. By default all users, contacts, groups, and Windows 10 computers are synchronized. You can change the filtering based on domains, OUs, or attributes.

Password synchronization synchronizes the password hash in Active Directory to Azure AD. The end-user can use the same password on-premises and in the cloud but only manage it in one location. Since it uses your on-premises Active Directory as the authority, you can also use your own password policy.

Password writeback will allow your users to change and reset their passwords in the cloud and have your on-premises password policy applied.

Device writeback will allow a device registered in Azure AD to be written back to on-premises Active Directory so it can be used for conditional access.

The prevent accidental deletes feature is turned on by default and protects your cloud directory from numerous deletes at the same time. By default it allows 500 deletes per run. You can change this setting depending on your organization size.

Automatic upgrade is enabled by default for express settings installations and ensures your Azure AD Connect is always up to date with the latest release.

Next steps to configure sync features

Topic	Link
Configure filtering	Azure AD Connect sync: Configure filtering
Password synchronization	Azure AD Connect sync: Implement password synchronization
Password writeback	Getting started with password management
Device writeback	Enabling device writeback in Azure AD Connect
Prevent accidental deletes	Azure AD Connect sync: Prevent accidental deletes
Automatic upgrade	Azure AD Connect: Automatic upgrade

Customize Azure AD Connect sync

Azure AD Connect sync comes with a default configuration that is intended to work for most customers and topologies. But there are always situations where the default configuration does not work and must be adjusted. It is supported to make changes as documented in this section and linked topics.

If you have not worked with a synchronization topology before you want to start to understand the basics and the terms used as described in the technical concepts. Azure AD Connect is the evolution of MIIS2003, ILM2007, and FIM2010. Even if some things are identical, a lot has changed as well.

The default configuration assumes there might be more than one forest in the configuration. In those topologies a user object might be represented as a contact in another forest. The user might also have a linked mailbox in another resource forest. The behavior of the default configuration is described in users and contacts.

The configuration model in sync is called declarative provisioning. The advanced attribute flows are using functions to express attribute transformations. You can see and examine the entire configuration using tools which comes with Azure AD Connect. If you need to make configuration changes, make sure you follow the best practices so it is easier to adopt new releases.

Next steps to customize Azure AD Connect sync

Topic	Link
All Azure AD Connect sync articles	Azure AD Connect sync
Technical concepts	Azure AD Connect sync: Technical Concepts
Understanding the default configuration	Azure AD Connect sync: Understanding the default configuration
Understanding users and contacts	Azure AD Connect sync: Understanding Users and Contacts
Declarative provisioning	Azure AD Connect Sync: Understanding Declarative Provisioning Expressions
Change the default configuration	Best practices for changing the default configuration

Configure federation features

Azure AD Connect provides several features that simplify federating with Azure AD using AD FS and managing your federation trust. Azure AD Connect supports AD FS on Windows Server 2012R2 or later.

Update SSL certificate of AD FS farm even if you are not using Azure AD Connect to manage your federation trust.

Add an AD FS server to your farm to expand the farm as required.

Repair the trust with Azure AD in a few simple clicks.

ADFS can be configured to support multiple domains. For example you might have multiple top domains you need to use for federation.

if your ADFS server has not been configured to automatically update certificates from Azure AD or if you use a non-ADFS solution, then you will be notified when you have to update certificates.

Next steps to configure federation features

Topic	Link
All AD FS articles	Azure AD Connect and federation
Configure ADFS with subdomains	Multiple Domain Support for Federating with Azure AD
Manage AD FS farm	AD FS management and customization with Azure AD Connect
Manually updating federation certificates	Renewing Federation Certificates for Office 365 and Azure AD

More information and references

Topic	Link
Version history	Version history
Compare DirSync, Azure ADSync, and Azure AD Connect	Directory integration tools comparison
Non-ADFS compatibility list for Azure AD	Azure AD federation compatibility list
Configuring a SAML 2.0 Idp	Using a SAML 2.0 Identity Provider (IdP) for Single Sign On
Attributes synchronized	Attributes synchronized
Monitoring using Azure AD Connect Health	Azure AD Connect Health
Frequently Asked Questions	Azure AD Connect FAQ

Additional Resources

Ignite 2015 presentation on extending your on-premises directories to the cloud.

IT Consultant inCOREporation.com