Office 365: Grant a User Full Mailbox Access to all Mailboxes
KB ID 0001466 Problem Obviously there are some security concerns about having a user with full mailbox access to all mailboxes! But that aside, I was using a third party Migration tool last week, and it needed to connect to every mailbox with full access rights to perform the migration. So this is how I did it; Solution Firstly you need to connect to your Office 365 tenant with PowerShell; Connect to Office 365 Exchange PowerShell Now...
O365: Enable Application Impersonation
KB ID 0001449 Problem While using a migration tool to do some ‘on-prem’ to Office 365 migrations I had to enable ‘Application Impersonation’ for my Office 365 user. The tool didn’t explain how to do that, so I had to work it out for myself 🙁 So to make things easier for everyone else, here’s how to do it. Solution From within the Office 365 portal > Admin > Exchange. Dashboard > Permissions...
Migrating Mailboxes From On-Premise to Office 365
KB ID 0001419 Problem This post continues from Part-One where we connected both our domain, and on-premise Exchange server to Office 365. Now we will add our public domain, and migrate our mailboxes. Step 3 Adding Domains to Office 365 Before proceeding you will need administrative access to your public DNS records so you can create new records. Log into Office 365 > Admin Console. Add a domain. Enter your public domain name >...
Office 365: Migrating To Exchange Online
KB ID 0001418 Problem This is Part-One of a migration from ‘on-premise’ Microsoft Exchange, to Office 365 (Exchange Online). I’m using my spare ‘test domain’ (.co.uk). And I’m using the 5 user E3 Office 365 subscription that the good folk at Microsoft let me have, as part of my MVP benefits. Note: I’m using Exchange 2016, with a ‘full-hybrid’ migration into Office 365. Step 1:...
Connect to Office 365 Exchange PowerShell
KB ID 0001410 Problem If there’s one thing thats grown on me it’s PowerShell, After the last few versions of Exchange you can’t really escape it. So now we have so many clients with their Exchange in Office 365. The ability to connect to that, and use all your usual Exchange commandlets is a bonus! Solution If you haven’t already done so, you need to ‘slacken‘ your signing policy, (a little) before...