

Microsoft Engineer
β - Featured Role | Apply direct with Data Freelance Hub
This role is for a Microsoft 365 Engineer on a 6-month contract, fully remote, with a pay rate of $55.00 to $65.00 per hour. Key requirements include 4+ years of M365 engineering experience, tenant-to-tenant migrations, PowerShell scripting, and Azure CLI proficiency.
π - Country
United States
π± - Currency
$ USD
-
π° - Day rate
520
-
ποΈ - Date discovered
June 7, 2025
π - Project duration
Unknown
-
ποΈ - Location type
Remote
-
π - Contract type
W2 Contractor
-
π - Security clearance
Unknown
-
π - Location detailed
Kansas City Metropolitan Area
-
π§ - Skills detailed
#Migration #CLI (Command-Line Interface) #SharePoint #Monitoring #JSON (JavaScript Object Notation) #Shell Scripting #DevOps #Security #Workday #Azure CLI (Azure Command Line Interface) #Azure #Logging #YAML (YAML Ain't Markup Language) #Scripting #Compliance
Role description
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
Job title: Microsoft 365 Engineer
Duration: 6-month contract- must be able to work on w2
Location-zipcode & Travel: Fully remote
Schedule: Approximately 8-5 CST (some flexibility with hours based on time zone, but preferred working hours are CST)
PR: $55.00 to $65.00 per hour, depends on experience.
Must haves:
β’ 4+ years of experience as an M365 Engineer with hands on experience in tenant-to-tenant M365 migrations, especially Microsoft Exchange
β’ Strong experience utilizing Bititan Migration Wiz
β’ Strong PowerShell scripting abilities within Core & Desktop functionalities (logging, error handling, permissions, and modular functions)
β’ Azure CLI / AzureAD / MSOnline / Graph SDKs
β’ Hybrid environment experience (Azure and on-prem)
β’ Strong understanding of security and compliance for group policy, role based access, OUs, etc
β’ Experience with JSON/YAML configuration driven tooling for repeatable migration tasks
β’ Must be comfortable with passing a 10-pannel drug test which includes Marijuana
Plusses:
β’ Migration experience with OneDrive, SharePoint, and/or Teams
β’ Experience with Remedy, ServiceNow, or DevOps practices
β’ Experience with Active Directory consolidation and cleanup
Day to day: As an M365 Engineer for Insight Global, your day-to-day responsibilities will involve using PowerShell (Core & Desktop) to create scripts with logging, error handling, and modular functions to check the current on-prem environment, including permissions and mailbox access. You'll develop scripts to recreate these settings in the M365 environment and verify the accuracy of the transfer. You'll also create bulk scripts for initial transfers and individual scripts for corrections, documenting and teaching the team how these scripts work. Utilizing Azure CLI, AzureAD, MSOnline, and Graph SDKs, you'll manage migrations with BitTitan MigrationWiz, addressing challenges like permissions. You'll track and document progress using tools like Remedy, ServiceNow, or DevOps boards. Your expertise in M365 tenant-to-tenant migrations, including mailbox, OneDrive, SharePoint, and Teams moves, will be crucial. Additionally, you'll support Exchange hybrid environments and handle Active Directory consolidation and cleanup, ensuring security, compliance, and change control throughout the process.
Roadmap: In the first 2-4 weeks, the M365 Engineer will focus on getting up to speed by conducting discovery of user accounts and information and developing a plan for account onboarding and creation from Workday and MEM systems in collaboration with the team. This period involves familiarizing with existing systems, processes, and tools. Following this, the engineer will spend time with the team designing a detailed playbook and developing scripts for one-off tasks and bulk loads, collaborating with the QA team to start mock runs, clean up, and refine processes. Testing will be conducted before migrations kick off, with a focus on identifying and documenting variances for user training materials. Starting mid-December, the engineer will provide post-migration support, addressing any issues that arise, ensuring smooth transition and user adoption of M365 systems, and continuously monitoring and optimizing system performance. This structured approach ensures a smooth transition through each phase, from initial setup to post-migration support.