Increase Attachment Size on Office 365

This article will help you Increase the Email Attachment size on Office365 via PowerShell. Login to Office 365 via Azure PowerShell. It’s advised to install the latest version of PowerShell. Prerequisite for Azure PowerShell is Microsoft Online Sign-in Assistant. You can download it from here. You can download the Azure PowerShell from the links below: Windows Azure Active Directory Module for Windows PowerShell (32-bit version) Windows Azure Active Directory Module for Windows PowerShell (64-bit version) Install the Sign-in Assistant, and Azure Active Directory Module, and launch Windows Azure PowerShell as Administrator (using Run as Administrator) Run the following commands to connect with your Office 365 account: Set-ExecutionPolicy = unrestricted $cred = Get-Credential -Credential $user Enter the credentials for your Office 365 Admin account and hit OK. Import-Module MSOnline  Connect-MsolService -Credential $cred  $msoExchangeURL = “https://ps.outlook.com/powershell/”  $session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri $msoExchangeURL -Credential $cred -Authentication Basic -AllowRedirection  Import-PSSession $session Now you can check the current attachment limit using Get-TransportConfig command, however this command will provide you will a lot of info that you may not need. Hence run the following to filter the required results only: Get-TransportConfig | FL *MaxMessage* Here you’ll get the following results: In above image, you can see how much data you can send in email as attachments to external and internal users. You can change this by running the following commands: Set-TransportConfig -ExternalDsnMaxMessageAttachSize xxMB Set-TransportConfig -InternalDsnMaxMessageAttachSize xxMB Note: Here, replace the xx with the about of data you would like to allow (as shown in the image). Repeat this steps for both Internal and External values. You can check the config again to see the new value is in...

Missing Start-OnlineCoexistenceSync when running DirSync via Powershell

Follow me issing Start-OnlineCoexistenceSync when running DirSync via Powershell: Recently working on an environment, I noticed that the Start-OnlineCoexistenceSync is missing when trying to re-sync the Active Directory with Office 365 via PowerShell. This was very helpful when we need to sync the changes manually to Office 365. You’ll also notice that DirSyncConfigShell.psc1 is no longer present in its default location of C:\Program Files\Windows Azure Active Directory Sync. This is due to the change version of the Directory Sync Tool currently running on your Computer. To know more about the Directory Sync tool revision history, click here. When you try to run command to sync the changes, you get the following error message: PS C:\> Start-OnlineCoexistenceSync The term ‘Start-OnlineCoexistenceSync’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:28 + start-onlinecoexistencesync <<<< + CategoryInfo          : ObjectNotFound: (start-onlinecoexistencesync:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException PS C:\> In order to manually sync the directory changes, follow the following steps: Open PowerShell Type: Set-ExecutionPolicy Unrestricted and hit return. Type: Import-Module DirSync and hit return. Type: Start-OnlineCoexistenceSync and hit return. Now that you have successfully forced the Directory Sync with Office 365 for changes. You may now want to check what’s synced and if it at all worked. Open the MIIS Client: “C:\Program Files\Windows Azure Active Directory Sync\SYNCBUS\Synchronization Service\UIShell\miisclient.exe” On the main screen that opens by default, you’ll see what all has been synced, and its detailed result. There are different section to this...