Some Notes on the Machines

This includes Exchange Online, Lync, and others:

https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US#BKMK_Portal-identity

This has been updated recently, and many changes have occurred. Ports have been reduced considerably, and many more FQDNs added.

It can happen fairly easily, that one or more user’s Office 365 login is wrong, and AD Sync fails to correct it. Here is a manual override, courtesy of the excellent Joe Busby.

1. On a domain controller, verify the AD username and proxy addresses is set correctly.
2. Connect to O365 Powershell on any machine with Powershell 5.1, and run this command:

Set-MsolUserPrincipalName -UserPrincipalName "user@old.address" -NewUserPrincipalName "user@new.address"

3. On the user’s PC:
   1. Navigate to Settings > Accounts > Access work or school
   2. Disconnect from any accounts linked to the new or old username
   3. Hit the [ + ] Connect button and provide the credentials to sign in to Office 365
   4. If their password has been changed since their account was synced up with the wrong username, the password may need to be reset.
   5. Remove any credentials from windows credential manager that match the old username.
   6. Check Outlook, you may have to create a new profile.

Excellent tool.

https://support.office.com/en-us/article/microsoft-support-and-recovery-assistant-sara-e90bb691-c2a7-4697-a94f-88836856c72f

There are many different products / licenses for Office 365, in several categories. The first item has links to the rest:

Business, general

Small business

Education

Government

Nonprofits

Home

Firstline Workers

The above suggested by the excellent Tharin Brown.

There is an alternative activation logon screen.

https://answers.microsoft.com/en-us/msoffice/forum/msoffice_account-mso_win10/unable-to-sign-in-to-office-2016-desktop-apps-sign/b32738c8-1b17-43d1-839b-cb97c8ae3c29

From the indefatigable Mike Crayton:

https://www.thecloudjournal.net/2016/08/reset-microsoft-office-product-activation-status/

https://gallery.technet.microsoft.com/office/How-To-Reset-Office-01cf9c07

This can help a lot when Office will not activate.

New version, as of 2018-10-29:

www.microsoft.com/en-us/download/details.aspx?id=47594

When this happens, do the following in Azure AD Connect:

1. In “Customize synchronization options”, disable (uncheck) the password hash sync option.
2. Wait for sync to complete, watching in the Operations tab of the Synchronization Service Manager.
3. In “Customize synchronization options”, enable (check) the password hash sync option.
4. Wait for sync to complete, watching in the Operations tab of the Synchronization Service Manager.
5. Check the Office 365 admin readout.

When recent versions of Outlook and other Office applications run certain plugins, sometimes the result will come up in a separate window called “AdxTaskPane”. To prevent this:

1. File > Options > General > User Interface options
2. Choose “Optimize for compatibility (application restart required)”
3. Restart the application

When you do an Office 365 / EOL migration with Azure AD Sync in place, mailboxes may freeze up, where in the O365 console under “Mail Settings” for one or more mailboxes, it says “This user’s on-premises mailbox has not been migrated to Exchange Online. The Exchange Online mailbox will be available once migration is completed.” One may spend a whole lot of time, even with Microsoft on the line, not fixing this problem.

There may be more than one cause. But a very important cause and fix is outlined here:

https://mikeparker365.wordpress.com/2016/01/07/how-to-filter-out-msexchmailboxguid-from-aad-connect-sync/

The gist of it is, one of the user attributes synched up from the on-prem server is “msExchMailboxGuid”, and this is trouble, because if this is synched up, EOL thinks it is trying to make a duplicate of an existing mailbox, rather than a new one, and it will not make a duplicate, it is in fact waiting for this attribute to be deleted before proceeding.

So what we do, is we go to Synchronization Service, right-click on “Active Directory Domain Services”, make sure “Connector Designer” is selected, and then scroll down to msExchMailboxGuid , and uncheck it. Then click OK.

The next step is to kick off a sync. The easiest way is in Powershell on the server which has AD Sync installed:

Import-Module ADSync
Start-ADSyncSyncCycle -PolicyType Initial

You can watch the progress in “Synchronization Service” if you like; after the two final exports are complete it is done. But we’re not done yet.

The next step, is to remove the licenses from all of the O365 accounts which are marked as not yet migrated.

Then run another sync.

Then add the licenses back.

And run another sync.

That did it this morning!