Category: Office 365

Connect PowerShell to Exchange Online / Office 365 / Azure
article #804, updated 55 days ago

The following method is the Microsoft-recommended current one. You may need to use Install-Module instead of Update-Module depending on pre-existing installations et cetera:

Set-ExecutionPolicy RemoteSigned -Force -Scope Process
Update-Module -Name ExchangeOnlineManagement
Update-Module -Name AzureAD
Update-Module -Name MSOnline
Import-Module -Name ExchangeOnlineManagement
Import-Module -Name MSOnline
Import-Module -Name AzureAD
Connect-ExchangeOnline -UserPrincipalName login@domain.com -ShowProgress $true

The following method is the previous, and is the one which works pre-Windows-10 and/or Powershell before 5.1:

$UserCredential = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection
Import-PSSession $Session -DisableNameChecking

When you’re done, be sure to do the following afterwards, or you may have to wait for automatic session expiration.

Remove-PSSession $Session

Categories:      

==============

Convert Exchange Online / Office 365 Mailbox from AD Sync to Cloud Only
article #1368, updated 136 days ago

In administrative Powershell:

  1. Install-Module AzureAD
  2. Install-Module MSOnline
  3. Connect-AzureAD
  4. Connect-MsolService

In Active Directory Users and Computers, remove the user object from OU being AD-synched. Then complete an Azure/AD sync cycle. Then:

  1. Restore-MsolUser -UserPrincipalName users_login_probably_email
  2. Set-MsolUser -UserPrincipalName users_login_probably_email -ImmutableId "$null"

Do the last step before the next automatic AD sync!

Categories:      

==============

Filter On-Prem Exchange Attributes for Azure AD Sync and Office 365 Migration
article #1379, updated 169 days ago

A couple of links:

https://itpro-tips.com/2019/this-users-on-premises-mailbox-hasnt-been-migrated-to-exchange-online/

https://answers.microsoft.com/en-us/msoffice/forum/all/this-users-on-premise-mailbox-hasnt-been-migrated/5735f499-7079-42a4-a5e9-8da275404d09

Categories:      

==============

Upload Huge PSTs to Exchange Online / Office 365 Using AzCopy
article #1373, updated 170 days ago

One can use this to import really big ones, dozens of gigabytes in size, imports which will crash, hang, and otherwise cough on Outlook very easily. Runs directly to folders inside of mailboxes. The amazing Yvonne Wynkoop found the first really good set of instructions we have seen:

blog.natfan.io/importing-psts

Mysteries do abound about the Microsoft-provided command line tool AzCopy, not the least being the fact that there is a version 10 and a version 8.1. Items as of this writing:

  • Version 8.1 is downloadable from Office 365, and works. Have no clue what 10 is for.
  • Usage and download of it, is now through Office 365 Security & Compliance, Information Governance, Import.
  • When you run it for an upload, add “/NC:2” to the end of the command line. This increases its speed and stability quite a lot, and prevents timeouts. Default is reportedly 24. Perhaps the developers are sitting on Google Fiber?
  • If it times out, just restart it carefully, it will usually continue where it left off.

If the above works for you, use the same number when downloading PSTs from eDiscovery, via registry edit:

https://docs.microsoft.com/en-us/microsoft-365/compliance/increase-download-speeds-when-exporting-ediscovery-results?view=o365-worldwide

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Client\eDiscovery\ExportTool]
"DownloadConcurrency"="2"

Categories:      

==============

Improve speed and prevent timeouts downloading PSTs from Office 365
article #1311, updated 174 days ago

If you let the eDiscovery Export Tool time out, it will eventually give you a link:

https://docs.microsoft.com/en-us/office365/securitycompliance/increase-download-speeds-when-exporting-ediscovery-results

which has the registry edit below. No explanation is given, but it does say that adjustment of the number (in some direction?) can help.

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Client\eDiscovery\ExportTool]
"DownloadConcurrency"="2"

Categories:      

==============

New Exchange Online connectivity for Powershell
article #1357, updated 267 days ago

New methods, reportedly considerably better, have not tested yet myself:

https://docs.microsoft.com/en-us/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2?view=exchange-ps

Categories:      

==============

Turn Off Azure AD Sync via Powershell
article #1334, updated 408 days ago

  1. Install the Azure Active Directory Module for Powershell.
  1. Connect to Azure AD, and disable sync:
Set-MsolDirSyncEnabled –EnableDirSync $false
  1. Check status, repeatedly, until it returns False. It can take 72 hours for sync to be fully deactivated.
(Get-MSOLCompanyInformation).DirectorySynchronizationEnabled 

Categories:      

==============

IPs, URLs, and Ports for Microsoft Cloud Services and Office 365 (Firewall Configuration)
article #800, updated 414 days ago

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.

Categories:      

==============

Manually correct Office 365 logins in AD Sync'd domains
article #1332, updated 419 days ago

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"
  1. 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.

Categories:      

==============

Fix Office, Outlook, 365 issues with Microsoft Support and Recovery Assistant (SaRA)
article #1316, updated 464 days ago

Excellent tool.

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

Categories: