Graph and PowerShell Blog

Shared Mailboxes
• Shared mailboxes need a license to be migrated, you can apply for 25 free Office365 licenses for 2 months.
• To migrate a shared mailbox you must set the password then enable the account before migration. After the migration the AD account should be disabled again.
• Max shared mailbox size is 50GB.
• MessageCopyForSentAsEnabled and MessageCopyForSendOnBehalfEnabled need to be set on the O365 mailbox even if set on-prem.
• MessageCopyForSentAsEnabled and MessageCopyForSendOnBehalfEnabled will not work if shared mailbox is on-premise and user mailbox is in O365 and vice-versa.

O365/M365 Groups
• Although writeback is enabled to on-prem AD this does not mean that O365 groups are Exchange aware. So all addresses should be user@domain.onmicrosoft.com and not your main external domain.
• Where the group is not used for email (ie most Teams) then you should not map the group to Outlook: Set-UnifiedGroup groupname -HiddenFromExchangeClientsEnabled:$true
• If you do plan to use mail functionality then you should enable subfolder creation and rules

User Mailboxes
• Delegated permssions need to be enabled - Set-OrganizationConfig -ACLableSyncedObjectEnabled $True .
• Any additional addresses must be removed - eg user@domain.local.
• The mailbox must have a @domain.mail.onmicrosoft.com address.
• AD accounts must be in an OU synced to Azure AD.
• User mailboxes should be assigned a retention policy and an auto-expanding archive.
• Set the mailbox language after the migration.
• After migration they should be assigned to the ExchangeOnline feature in O365 licensing.

Graph and PowerShell Blog	Articles 2024 Advanced Postfix configuration Installing Exchange 2019 in Azure Landing Zone Upgrading PHP on Windows Adding a Postfix server for relay to O365 O365 Integrated Apps troubleshooting Domino and O365 Co-existence Delegate Control in AD App mail relay via HVE Setting up Mail Relay with HVE Getting BIMI certified Orbea Occam SL H30 Installing FreeSat and Saorview Changing broadband provider Replacing a DIN timer on fuseboard Outlook Desktop Notifications stop working Outlook folders keep moving sort order Teams report uploading to SharePoint with Runbooks Teams PowerShell module can't run CS cmd as App 2023 Cannot map new Shared Mailboxes in O365 Renewing an Exchange 2016 certificate Connect to Compliance PowerShell behind a Proxy Sensitivity Label not shown in Outlook Client Room Finder Error in Outlook Teams not showing Rooms Teams unable to open file Unable to review quarantined mails for shared mailbox Set Locale for various Apps Delegate Sent Items placed into external Tenant Overview of Microsoft Support cases When centralized mail sends via O365 Cleaning up your Windows DNS server Set OneDrive for Business Locale O365 Migration Tips Reporting on successful Azure logons IIS Mapi Queue full with NetScaler Secure Office365 reports with a certificate Using Graph to send emails with inline images Visualizing Graph data with Google Charts Keeping a log of NetScaler AlwaysON connections \| About \| Links

Some tips that can help when migrating mailboxes to O365 08-Mar-23 Shared Mailboxes • Shared mailboxes need a license to be migrated, you can apply for 25 free Office365 licenses for 2 months. • To migrate a shared mailbox you must set the password then enable the account before migration. After the migration the AD account should be disabled again. • Max shared mailbox size is 50GB. • MessageCopyForSentAsEnabled and MessageCopyForSendOnBehalfEnabled need to be set on the O365 mailbox even if set on-prem. • MessageCopyForSentAsEnabled and MessageCopyForSendOnBehalfEnabled will not work if shared mailbox is on-premise and user mailbox is in O365 and vice-versa. O365/M365 Groups • Although writeback is enabled to on-prem AD this does not mean that O365 groups are Exchange aware. So all addresses should be user@domain.onmicrosoft.com and not your main external domain. • Where the group is not used for email (ie most Teams) then you should not map the group to Outlook: Set-UnifiedGroup groupname -HiddenFromExchangeClientsEnabled:$true • If you do plan to use mail functionality then you should enable subfolder creation and rules User Mailboxes • Delegated permssions need to be enabled - Set-OrganizationConfig -ACLableSyncedObjectEnabled $True . • Any additional addresses must be removed - eg user@domain.local. • The mailbox must have a @domain.mail.onmicrosoft.com address. • AD accounts must be in an OU synced to Azure AD. • User mailboxes should be assigned a retention policy and an auto-expanding archive. • Set the mailbox language after the migration. • After migration they should be assigned to the ExchangeOnline feature in O365 licensing.