In today’s competitive business environment, companies need to ensure that their new hires have a smooth onboarding experience. Part of that is to have all their accounts, access roles, and other services ready to go on day one. Delays can cause poor satisfaction and...
Bits & Bytes
The BitTitan Blog for Service Providers
When migrating customers, managing mailbox permissions is a process filled with opportunities to make time-consuming, costly, and frustrating errors.
Redundant manual tasks, inconsistent scripts, varied deployment methods, and a lack of prescriptive guidance can lead to failed or faulty mailbox migrations.
Without version control and centralization, migrations can become frustrating for both customers and engineers. MSPComplete helps IT service providers create one source of knowledge that can be easily updated and shared for consistent, efficient service delivery that prevent problems from the challenges below.
Mailbox permissions are a missed opportunity to reduce mistakes and costs through automation.
When migrating mailboxes—whether from an on-premises server to the cloud, or from tenant to tenant—engineers often work locally when they write scripts. To successfully migrate mailboxes, they must first identify users that have access to each other’s mailboxes, line up connections between accounts, and flag additional configurations that affect the organization’s users.
The differences across users’ permission makes it difficult to avoid writing custom script for each project. Some customers may have permissions for Full Access and Send As, while other customers may only want to migrate Full Access permissions. A significant amount of time is lost when constantly writing custom scripts and the practice itself undermines efforts toward standardization.
Engineers can write and modify a single script that accommodates all the combinations of permissions in Office 365 and Exchange. By using input variables, engineers can select the correct permissions for each customer without downloading and then modifying a local script.
Custom scripts make version control and efficiency a challenge.
While custom scripts allow engineers to run variations of a standardized migration, it’s not always efficient or profitable. Over time, many local copies can be produced, meaning more variations of scripts that must be managed so as not to misuse them on other projects.
Even if engineers have the perfect script for a process, it’s often stored on a local drive, requiring extra time to search for and download the script. Most of the IT services providers we’ve worked with don’t have an efficient way to associate their scripts directly with their documented processes.
With Runbooks in MSPComplete, scripts are matched to the correct task with specific instructions for deployment. Once the best-script is selected and updated, it can even be executed directly from the platform.
Explore out-of-the-box migrations and other Office 365 services.
MSPComplete features a growing Library of out-of-the-box Runbooks for a variety of cloud services, including BitTitan migrations, Datto backup, and many other Office 365 tasks—all readily customizable to align with the unique way you deliver services.
Want to see more?
Subscribe to see more examples of PowerShell Automation in MSPComplete, including how to securely add users in Office 365. Stay informed of the latest demonstrations and new features!
Ready to dive in?
Learn more about how MSPComplete can help you ensure repeatable, scalable, and profitable IT services delivery through centralization and automation of scripts, and standardization of practices.
Get started with MSPComplete today.
Register for a FREE BitTitan Account
Create an account now and start planning your project.