FastTrack Tips

Who is linked to whom in your spider web of mailbox permissions. Migration batch permissions analysis.

Larry Dunnewin — Tue, 16 Apr 2019 14:47:08 GMT

You’re going to migrate mailboxes from Exchange 2010, 2013 and/or 2016 to Office 365. You know you have many mailbox permission threads between delegates, delegators, shared mailboxes and users. How can you gather all those permission threads and determine who to migrate with whom to keep those permissions together? What do you do when the script indicates a minimum batch larger than you want to migrate all together? The Find-MailboxDelegates script on GitHub will gather your ‘spider web.’ It will analyze them into minimum batches of mailboxes that should migrate together. When a minimum batch is too large is where the Batch-analysis spreadsheet will help. The spreadsheet will help you see the threads between mailbox and user in that large web. Using the Find-MailboxDelegates script, you gather all 4 mailboxes permissions and have the resulting output files “find-mailboxdelgates-permissions.csv” and “find-mailboxdelegates-batches.csv.” The batches.csv shows you have one or more migration batches that contain too many mailboxes to migrate all together. The analysis spreadsheet can help you manage and understand what threads are between a subset of mailboxes from that large batch and those not migrating. It doesn’t eliminate cross forest permission issues but allows you to visually see the threads and understand whose permissions will be ‘split’ for any potential migration user batch. It also lets you see all the permission threads as they exist before migration for one mailbox or many. New: a Migrated Mailboxes tab has been added to allow for excluding migrated mailboxes from the analysis without having to rerun the script or edit the permissions output. You may decide to gather potential migration batches based on ‘non-permissions’ attributes, i.e. department, site, team or building etc. Once you have ‘potential user batch’ subsets, the spreadsheet will help you analyze the permission threads are between mailboxes and user/delegates. Equipped with your potential batch user lists and the find-mailboxdelegate-permissions.csv file you are ready to use the spreadsheet for ‘what if’ analysis It may be worthwhile to sort the Find-MailboxDelegates-Permissions .csv by mailbox and user. You can also sort your proposed batch list. Once you start moving addresses from results to potential user batch while analyzing, it's ok if you create duplicates in your user list. It won't affect the results. If your Find-MailboxDelegatesPermissions.csv file was edited and saved, the three original columns and header row format must remain as created by the script; no additional columns or data added.

Setup instructions:

When you first open the spreadsheet, you will be in the Setup for PermissionsOutput worksheet tab: Click the blue Setup button. Use the file dialog window to browse to your Find-MailboxDelegates-Permissions.csv file and click Open. The import macro will finish in the Batch Users worksheet tab. This is where you paste in a potential user batch list starting in Cell A3. Note: if your permissions.csv file is larger than 200K rows, it will not correctly function. Prior to loading into the spreadsheet, you can delete all the rows in the permissions.csv file that have ‘mailbox,none,none’ in a row. If it is still too large, you can modify the macros and named ranges in the spreadsheet to handle the file size (see below.)

Analysis Instructions:

Paste a proposed user batch list in column A under "Potential User Batch." Click the green ‘Run Analysis’ button. The results will display a list of mailbox and users that have shared permission threads that will be split cross forest if that potential batch is migrated. You can then add/remove mailboxes from the potential batch based on the results. Then rerun the analysis to see how the permission threads changed. The column "Who is in Batch" indicates the mailbox or user is migrating in the potential batch. ‘User in batch’ is highlighted in yellow to more easily glance at the results and see which is migrating when you have a larger list. The green buttons allow for looking at specific permissions you gathered with the script. Filtering out the other permission types from the results. i.e. you can see only delegation 'GrantSentOnBehalfTo' permissions even though your csv import included all 4 types. Similarly, with 'send-as only' and 'calendar only'. When using the 'All Up' macro you will also see when both the mailbox and user/delegate are in the batch and it shows highlighted green. That indicates the permission thread is supported after the migration because both are in the batch. “All Up" shows all the permission threads, including 'full access' that is supported cross forest, regardless if they would be split or not. New: All up still excludes the migrated mailboxes. New: Once you migrate mailboxes, paste those addresses in the Migrated Mailboxes tab. That will allow for future potential batch analysis to exclude those migrated mailboxes from showing as split permissions as they are already in Office 365. If you want to see all permissions including the migrated mailboxes, copy all the migrated mailbox to column B and delete all from column A. To exclude again, copy back to column A. As you migrate mailboxes in batches and want to continue to analyze remaining mailboxes for permissions, you should remove the migrated users from the permissions.csv; basically, pare down to the remaining mailboxes. The easiest way is to remove them from all rows where they exist as either mailbox or user in the permissions.csv file and then import into a newly downloaded (empty) batch analysis spreadsheet. You don’t have to rerun the find-mailboxdelegates script to gather the remaining permissions. However, if you’d like to see the overall batching of the non-migrated mailboxes, you can rerun the script with the -batchusersonly parameter with the reduced find-mailboxdelegates-permissions.csv file as described in the Find-mailboxdelegates script instructions on GITHUB.

Note: If your permissions output.csv is longer than 200,000 entries, you will have to replace “J199999” in the Setup macro to be large enough. Also named ranges ATTALL, ATTCOMPARE and ATTDATA need rows increased.

(Special thanks to Chris Kadlick.)

Is ExpressRoute for Office 365 for me?

Euclides Miguel — Mon, 08 Oct 2018 00:00:02 GMT

“Is ExpressRoute for me?” seems to be a recurrent question these days. And from Office 365 standpoint, the answer is probably not for the clear majority of customer asking that question. I will tell you why: Simply put, Office 365 is designed to work via the internet. Securely and reliably. Moreover, many of the services require some level of Internet connectivity and none will work exclusively with ExpressRoute (with no Internet at all) as you can read at the Office 365 endpoints article. Of course, there are few situations where ExpressRoute makes sense, but they don’t come across very often. Before you ask, those situations usually involve regulatory requirements. And even in those cases, you must perform a complete network assessment before going down the ExpressRoute way. Ask your account team, your FastTrack team… any of us, and we will point you in the right direction.

But why, why?

If you think about how users connect to Office 365, it is a truly distributed application, with endpoints all around the world. I wrote an article about getting your DNS right that discusses this topic. It is directly related to the case here: We will do our best to make sure you access our services in the fastest way, pointing you to the closest Office 365 endpoint, no matter where you are. Using dedicated network circuits makes it more likely that you would have to back haul traffic across a WAN before connecting to that circuit. That back haul adds latency and single circuits cause single points of failure. It’s better on both counts to have cheap local ISP connections that are closer to the user and route network traffic more directly to Office 365 network endpoints. The goal is to minimize network latency and reduce the round-trip time (RTT) from your network to Microsoft’s global network. You can read more about optimal network architecture and Office 365 Network Connectivity Principles.

Yeah, but I still think ExpressRoute can help me

If you are still not convinced, check the scenarios where ExpressRoute may be considered:

Situations where you believe that a direct network connection to Microsoft can help you meet regulatory requirements for some Office 365 services.
Your Internet egress topology does not meet the requirements and best practices for Office 365 Exchange, SharePoint or Skype for Business and cannot be tuned, changed, or scaled to support those in the future, while a specific network design based on ExpressRoute peering overcomes such constrains.
Office 365 performance is impacted by network deficiencies that ExpressRoute can address. It is important to clearly understand the root cause for any performance issue (for example, by performing a network assessment), and subsequently confirm that the ExpressRoute network design will remediate that issue.

If one of the three scenarios above describes your environment, contact your account team and start working on a network assessment. Then you have everything you need to reach a final decision.

Summing it up

If you simply want a secure, stable, and performant connection to Office 365, you don’t need ExpressRoute. Office 365 is built upon Microsoft Datacenter’s network which has points of presence in all the continents but Antarctica, that can take you to your data with the best performance. However, you are on one of the three scenarios we say ExpressRoute can help you, please work on the network assessment and with your account team at Microsoft to start the process with us. The Office 365 networking product group would like to learn about your networking challenges with Office 365 connectivity. Please comment on this blog to start a conversation.

Resources

Editing distribution list membership after migrating to Exchange Online

Rodrigo Moreno — Tue, 02 Oct 2018 17:33:23 GMT

So, your users manage distribution lists with Outlook. And then you decide to move to Exchange Online just to figure they will not be able to manage those DLs with Outlook anymore. Now what? You have options and one of them is discussed here: Allowing your users to edit the groups using only Windows. That’s what we did in the company I work for. The first thing you must ensure is that your groups are configured properly: Your groups must be configured to allow managers to edit the membership list. If you are interested, you can start researching a way to check those boxes using PowerShell at Manager can update membership list Part 1. Now that we cleared the smallest pre-requisites list in the world, let’s go to the fun part: The user will log on in a computer member of the domain using its credential and open the Windows Explorer.

1. Open the Windows Explorer
2. Click on the Network icon, on the bottom-left side of the screen
3. Click on the Network tab, on the toolbar (ignore this step if you are running Windows 7)
4. Click Search Active Directory

1. Type the name of the distribution list you are looking for in the Name text box
2. Click the Find Now button
3. Double-click the group you want to edit

Now you can add and/or remove members from the list. Let’s you wan to add the new guy to the list.

1. Click Add

1. Type the name of the user you want to add to the list
2. Click Check Names
3. Click OK

1. Now you click OK and close the search window.

Voilà! Now you must keep in mind you just made a change in your local Active Directory. I can take a while for the change to replicate across local domain controllers and to the cloud. That time can be different for you, but for us, we usually see everything synchronized within 60 minutes.

BONUS: You can create a GPO to distribute a shortcut to your users’ desktops with the following command: “Rundll32 dsquery.dll OpenQueryWindow”. That would get them directly to the query window.

What the heck happened - My largest user group changed from Semi-Annual Channel to Monthly Channel?

randyi — Mon, 01 Oct 2018 00:00:51 GMT

Regarding Office 365 ProPlus updates, some IT admins want total control (which often turns out to be the illusion of control). Some follow the recommended practices, which is receiving updates via CDN (Content Delivery Network). Below is a scenario that can happen to YOU if you are managing Office 365 Pro Plus updates locally. Here’s what can get you in trouble: You have some local folders/shares that your XML files point to for UpdatePath, and most of your user population is on the Semi-Annual Channel, which gets feature updates twice a year. One morning you come in and say “, all my users are on Monthly Channel. I don’t want them to get feature updates that often. What happened!?!?!?!?” Well, here’s what probably happened: Someone (I’m sure it wasn’t you…) or some process accidentally dropped an updated build for Monthly Channel in the folder/share that you have specified as the Update Path for the Semi-Annual Channel. When you choose to manage the updates on your own, you are responsible for keeping track of which channel is where. If the Office 365 ProPlus client checks its UpdatePath and sees a build number more recent than the client has installed, it updates to that build REGARDLESS of what channel is in the UpdatePath or what channel was originally specified during setup. If you get your updates from CDN, then the CDN maintains the channel specified during setup, and does not change it unless an admin runs another setup configuration or applies a different Group Policy. If you get the updates from CDN, you don’t have to worry about the client changing channels, if you manage the updates yourself you DO have to worry about getting that right. If you want to see the described behavior above for yourself, it is simple to reproduce, just follow the steps below: NOTE: Only perform this on a test computer for demonstration purposes, DO NOT perform this in production. It will yield undesirable behavior.

Remove any existing version of Office using Control Panel – Programs and Features.
Create a C:\ODT folder.
Download the Office Deployment Tool from https://www.microsoft.com/download/details.aspx?id=49117 to the C:\ODT folder.
Run the Office Deployment Tool executable, deploying it to the C:\ODT folder.
Save Config1.xml and Config2.xml listed below into the ODT folder.
Create an C:\O365PPSetup and a C:\O365PPUpdate folder.
Open an Administrative Command Prompt and run “Setup /download config1.xml” without the quotes. (This will download the Office build to the specified folder).
When the command prompt returns after the download has finished, run “Setup /configure config1.xml” without the quotes.
Check Excel Version (Go to File – Account and note the Channel and Version).
Run “Setup /download config2.xml” without the quotes.
Manually trigger an Office Update from File – Account – Update options.
After the update check Excel Version and note both the channel and version have changed.

This demonstrates how an admin must be extremely careful if they are managing updates locally on their own rather than just getting updates from the CDN (Content Delivery Network).

Config1.xml

Config2.xml

NOTE: At the time this post was written the version number listed in Config1.XML was 1 version older than the latest build. Over time as new versions come out the delta between current and the version specified get greater. To update the version number, you can create a similar file using https://config.office.com making sure not to get the latest version for the first step or just use it to check the version number and modify the Config1.XML accordingly.

How many of my licenses are in use?

Euclides Miguel — Fri, 28 Sep 2018 12:28:25 GMT

Yesterday a good friend of mine, who also happen to be one of my customers, asked an interesting question that no other customer asked me: “Is it possible for us to receive some kind of alert when I’m running out of licenses in Office 365?” That question got me thinking. And to be honest, I didn’t know the answer… so I went looking for and figured we do not have such alert yet. Worry not, because PowerShell is your friend, and nothing is lost until you say so. Turns out that AureAD PowerShell module can list all the available subscriptions with the respective numbers of enabled and assigned licenses. The first thins you must do is to install the AzureAD PowerShell module in your computer. The procedure is documented here. Then you connect to Azure AD:

Import-Module -Name "AzureAD" Connect-AzureAD | Out-Null

And then…

Get-AzureADSubscribedSku | Where-Object {$_.CapabilityStatus -eq "Enabled"} | ForEach-Object { New-Object -TypeName "PSObject" -Property @{ SkuPartNumber = $_.SkuPartNumber ConsumedUnits = $_.ConsumedUnits PrepaidUnits = $_.PrepaidUnits.Enabled Consumption = ($_.ConsumedUnits / $_.PrepaidUnits.Enabled).ToString("P") } } | Format-Table -Property SkuPartNumber, PrepaidUnits, ConsumedUnits, Consumption

If you save this code as a PowerShell script, it will give you an output like the one bellow: How cool is that?

Adopt faster using Play Sessions

Camille Jimenez — Thu, 28 Jun 2018 18:16:09 GMT

I have always struggled with learning new topics from online videos. Videos are definitively helpful, and I know a lot of people that learn how to cook, earn IT certifications, or even fix a car just by watching videos, but not me. I prefer classroom training because I get to learn from someone in person and I get the chance to practice, ask questions, and make mistakes. The more mistakes I make, the more expertise I gain about the topic, because I know what can go wrong and how to troubleshoot when problems arise. This is why I have always believed that to have better adoption rates employees should become experts in O365 workloads and we should train our people to become trainers and let them train stakeholders or champion groups with practice sessions. Some time ago, I started an experiment with my colleague to create an adoption whiteboard session for the FastTrack Center in Las Colinas. We had the idea of having FastTrack Managers and FastTrack Engineers meet in person in a conference room to learn new adoption topics, so we could better explain adoption trends to our customers. I then mentioned the idea of what we call now Play Sessions. The name might sound silly but let me explain. One of the first meetings included a “Play Session” was for MS Teams. We decided to invite a Teams SME to do a demo and an FM to present a customer facing deck for the first half of the session. People loved it, and although they didn’t ask any questions, they seemed to understand. For the second half of the session we created a game, a Play Session, and that's when things got get interesting. I created a list of things to complete in 30 minutes, we created a test team in MS Teams, a scoreboard, and then grouped people in pairs. They had to complete all the tasks from the Play Session, and every time they finished one they had to run to the scoreboard, and they would earn one point. The pair that finished first would win our first Play Session. Then… something amazing happened! Everybody started asking questions, talking amongst each other, and running to the scoreboard. We discovered that even the FastTrack Engineers we thought understood the first half of the meeting didn’t understand how to do some things that the SME talked about in his demo. At the end of the session, everyone was excited to learn more about other workloads in future sessions. In the survey, participants mentioned that they felt more prepared to talk about MS Teams to customers and do this same session in their demos. People that were not using Teams started to use it often. They all practiced, made mistakes, learned, and had fun at the same time. We have many great resources to share for O365 learning, but some FMs are going an extra mile and generating play sessions with their customers because they want them to adopt more workloads and to adopt them faster. Here is what we did in the play session: Instructions:

Navigate to MS Teams.
You are already invited as an owner to our Play Session Team called “ Teams- Play Session.”

Follow these instructions. Each time your team finishes a task, go to the whiteboard and check the task that you completed.

Task	Description
1	Navigate to the Team “Teams- Play SESSION” and show how you feel right now with a GIF.
2	Create a Channel under that Team and name it with an original name.
3	Install these applications: Polly, Planner, One Note, and Power BI in the Channel that you just created.
4	Click the Files tab in the Team and edit the document called “TESTING 1 2 3.” Share with us what you thought about the SME session.
5	Navigate to the team and @mention someone.
6	Navigate to the Store and install the “Growbot” app and send a Kudo to your team member in your Channel.
7	Send a Kudo with Growbot in the Team.
8	Create a poll in the Team using “Polly,” make sure to answer other team polls.
9	Navigate to Outlook and send an e-mail to the Teams e-mail address.
10	Create a Teams meeting from Outlook for today at 9 P.M. and send it to your other Team member.
11	Find for a GIF of your favorite movie and post it in your Team.

Why don’t you try doing an exercise like this for your group or team? The adoption process will quicken, they will learn about the workload, and will be entertained at the same time. Collaborators of the play session: Camille Jimenez (Relationship Manager), Priya Vanka (Relationship Manager), Alicia Sanchez (FastTrack Manager), Alejandro Lopez (FastTrack Engineer – Teams SME)

Pre-flight and migration tool update

Euclides Miguel — Thu, 26 Apr 2018 10:41:25 GMT

We received some feedbacks since the Pre-flight tool was published last year on GitHub: from bugs (yeah, those pesky things) to new features. Focusing on the features, it’s about time to make a review on them:

Pre-flight

This is what that motivated me to write the code: Giving customers a sample tool that helps checking objects before requesting a mailbox move. It is documented here. Customers using FastTrack Center services have a pre-flight tool available. But I felt customers outside FTC could use some help and guidance as well, so this script/tool came to light.

Export migration command (updated)

The tool originally exported the migration scripts using the New-MoveRequest cmdlet. But it used New-MigrationBatch for migrating mailboxes directly from the tool. Now we use the New-MigrationBatch for both operations. Why did we use different approaches for migrating mailboxes and exporting migration script? To give customers the opportunity to learn two different ways to accomplish the same thing. Remember this is a sample script. But why did we change the behavior? One, for consistency, two, to make it work with the report script and three, New-MigrationBatch is faster. Not to be confused: the migration itself tends to take the same amount of time for both New-MigrationBatch and New-MoveRequest, but you don’t have to keep PowerShell running a set of cmdlets that can take a lot of time to complete.

Migrate mailboxes (updated)

At the beginning the tool only allowed you to immediately start the migration. But then the Exchange Team introduced a feature that allows customers to schedule the migrations, which is awesome by the way. The ability to schedule migrations (alongside with reporting) was an appealing topic for customers using FastTrack Center migration services. But then again… what about customers not using our services? Now the tool mimics the Exchange Admin Center migration options (manual, automatic, scheduled) and customers can easily schedule their migration jobs directly from the Pre-flight & Migration tool. You can see the details at Mailbox migration – Do it yourself guide.

Import list of mailboxes for pre-flight or migration (new)

The official Pre-flight tool we use within FastTrack Center requires customers to build a CSV file with the list of mailboxes to be checked and load it into the tool. Me personally didn’t like the idea and would rather pull a list of mailboxes available for migration from Exchange Online. Guess what? I was wrong. Lots of people requested this feature. It appears that this helps a lot, because you do not have to select each mailbox and add it to the list for pre-flight/migration. That’s how it works: You open the tool, connect to Exchange Online and simply click the Import button. Or click the File/Import… menu.

Sort (new)

The original version of the tool listed the mailboxes available for migration in a less than optimal way. To say the least. One of our customers asked why didn’t it sorted the mailboxes before presenting them in the Available mailboxes list. I confess I was ashamed because it was so simple to implement yet I didn’t think of it… Good thing we have customers that keep us true. But then I felt we could go further and added the ability to sort the list both ascending or descending. By display name or e-mail address. And that is what I later coded into the tool. Try it on clicking on the list headers!

More information on the lists (new)

It has to do with the sorting thing. First, it was not possible to do the sorting in an intuitive way without column headers, so I changed the control from TreeView to ListView. List view is much easier to work with for those new things you were asking. Then I had the columns, so why not listing the display name in addition to the SMTP addresses?

Search (new)

A colleague in FTC bugged me with this. I guess he has a customer that was bugging him about this one as well. And I am glad they did, because I got to learn something new! The idea is simple: You type the name of the mailbox you want to find and the list scrolls to it. Then you can do whatever you need: Select, deselect, add to the selected list, remove from it.

Works with MFA (new)

One of our customers decided to give the tool a try. They were seriously considering doing the migration by themselves (they did it beautifully latter on) and needed a way to check for foreseeable issues. But their identities were federated and they did not use WS-Trust. Meaning that the process described at Connect to Exchange Online PowerShell does not work for them. They use Connect to Exchange Online PowerShell using multi-factor authentication instead. Now the tool checks what kind of connection it needs to use and adjusts itself to the situation: If you start it from PowerShell with the Exchange Online module installed, it will use MFA, otherwise the classic method will be used.

About feedback and open software

All the changes above were driven by feedback. However, let’s not forget this tool is an open software under the MIT license. So, every feedback is welcome as well as any changes to the code. Be bold and if you feel like, write the piece of code you think this tool deserves.

Completing individual move requests in a migration batch (changed behavior)

Euclides Miguel — Thu, 15 Mar 2018 16:52:04 GMT

Recent changes in Exchange Online changed the way we finish individual migrations within migration batches. We used to run Set-MoveRequest -SuspendWhenReadyToComplete $false and Resume-MoveRequest, but that does not work anymore and the move requests get stuck in Synced state. Imagine you have a migration batch set to start automatically and complete manually. Like the image below: Exchange Online will synchronize the content from Exchange on-premises to the cloud and keep them synchronized with subsequent incremental syncs. Now let’s say you have 100 mailboxes with Synced status but you are ready to complete the migration for only half of them. Since the SuspendWhenReadyToComplete switch does not work anymore, that is what you have to do:

For each of the mailboxes you plan to complete the migration, set the CompleteAfter date: Set-MoveRequest -Identity "user1@contoso.com" -CompleteAfter (Get-Date)
Resume the move request: Resume-MoveRequest -Identity "user1@contoso.com"

That should do the trick. All the best!

Have fun with your OOF

Euclides Miguel — Thu, 15 Mar 2018 00:00:09 GMT

Believe it or not, people at Microsoft have fun. I do not mean we have fun with our jobs, which we do (my boss might be reading this… who knows?). We have fun with ourselves, the silly things we do every day, the dumb things as well… The other day I sent an e-mail to a friend of mine, who is a Technical Account Manager in Brasil and was on vacation. I received the hilarious OOF message bellow: For those of you who cannot read Portuguese, it translates to something like this:

JP is not authorized to monitor his e-mail because he is on well-deserved vacations Action Required Wait for JP to return or follow the steps bellow. After another year of hard work, JP has managed to detach himself and is enjoying a deserved break. His good life lasts from February 10th to 25th. “Wow… but I urgently need to speak to someone at Microsoft!” Well… the Technical Account Managers at Microsoft have something we call backups for those situations. Rodrigo is JP’s backup. He is an excellent professional and he is aware of the things going on with JP’s customers during his 2-week absence.

And it goes on… I dug a little and found out JP was not the first one to use Exchange Online NDR2 message as template for it OOF. That prize goes to another good friend of mine, an Exchange PFE also based here in Brasil. That’s his OOF: Rodrigo has an acid, sometimes sarcastic, sense of humor, so you should consider this OOF was internal only and nobody was offended by it. I guess… To be honest, I like Rodrigo’s style just a little better. But, you know… we are both engineers and engineers tend not to think before saying things they latter regret. If you like a funny OOF message but you want to restrict it to you coworkers, that’s how you do it:

Copy the OOF message below (between horizontal bars)
Open Outlook
Click the menu File
Click Automatic Replies button
Check the Send automatic replies option
Paste the OOF message and adjust it to meet your taste
If you want an external OOF message, select Outside My Organization tab and write your external OOF message

Your message to Euclides won't be read soon because he is on well-deserved vacation.

Euclides wasn't found at Microsoft. (We swear we looked under the table too)

You

Office 365

Euclides

Action Required

Recipient

Wait until he is back

How to Fix It

Even considering the mail tip with my OOF message, you decided to send me a message anyway... That is what you can do now:

· Reboot your computer - The Email Server is unable to verify your server connection. Your message has not been delivered. Try to restart your computer and send it again. (Seriously, this is just a joke... don’t do that).

· Wait for me to get back - You are receiving this automatic notification because I am out of the office. If I were in, chances are you would've not received this. So, seat tight and wait for my return. Please consider that even when I get back, it will take a while for me to answer your e-mail (Just saying... it will take a while.).

· Try not to fill my mailbox up - Please be patient and your mail will be deleted in the order it was received. If you send me multiple e-mails, I will randomly delete your e-mails until it is pared down to one. Choose wisely. Please note that you already sent me one e-mail. (Again, just saying...).

If the problem continues, you are not waiting long enough... Feel free to send your message again. But only after I return, right?

Did you like this OOF message? See how it was done at the FastTrack Tips Blog.

Have fun!

Exchange Online migration reporting

Euclides Miguel — Thu, 15 Feb 2018 00:00:35 GMT

This article is a follow-up to the Mailbox migration – Do it yourself guide article. It is also a product of your direct feedback, so thank you! Every migration batch you create is listed at the Exchange Online Admin Center (EAC, recipients, migration). You can open the migration batch details and scan for the information you need or you can use PowerShell to get specific details: You can also use PowerShell to create more elaborate reports. In this post I will show a migration reporting tool you can use as example for your customized reports.

A sample tool for migration reporting

The first thing you need to do is to download the reporting tool. It is available at Pre-flight, in GitHub. You must download the script itself and the images folder: Now you run the script and click the Configure button, which will open a graphical interface: You enter your cloud credential, click Ok… And then click the Connect button: Now you simply select the migration batches you want to report and click the Generate report button. Note that all the batches are selected by default. It will open a dialog, where you select a folder, name your report and click Save: That’s it! Now the toll will get the details for each request inside the selected batches and write:

An html with general information
A CSV for each batch with detailed information

Now please leave your feedback: Tell us what you like, what you do not like or what you think this sample tool should do. Thanks!