Case Studies
Microsoft 365 tenant-to-tenant migration
The task is to transfer all services and data to another tenant due to the division of companies and the change in the location of the head office, which purchases the services.
Source data: A logistics company with over 600 users, a hybrid deployment scheme for Microsoft 365 with Azure AD and AD, a hybrid deployment of Exchange and Exchange Online. Active use of services: Exchange (2TB), OneDrive (3.5TB), SharePoint (0.5 TB), MS Teams (1.5 TB), Planner.
Implementation period: 2 months.
Results: The breakup of the old hybrid scheme and the creation of a new one with a new tenant, the transfer of all user data Exchange Online, OneDrive, SharePoint (file storage), MS Teams (teams, channels, messages, files), Planner for Teams. Domain name switching between tenants.
Implementation period: 2 months.
Results: The breakup of the old hybrid scheme and the creation of a new one with a new tenant, the transfer of all user data Exchange Online, OneDrive, SharePoint (file storage), MS Teams (teams, channels, messages, files), Planner for Teams. Domain name switching between tenants.
Google Workspace to Microsoft 365 migration
The task is to transfer mailbox data, Google Drive - Personal data, Google Drive - Group data, Calendars, and Contacts from Google Workspace to the infrastructure of the parent company, which is based on Microsoft 365, to maintain continuity for the fastest possible adaptation of employees in the new environment.
Source data: Trade company with more than 400 employees who have been actively working with Google services for a long time - Mail (Contacts / Calendar - 4.5 TB), Google Drive (6 TB), Documents Online (Docs, Sheets, Slides).
Implementation period: 3 months.
Results: Transfer of all mail, including contacts and personal calendars of all employees from Gmail to Exchange Online, transfer of personal data from Google Disk to OneDrive, migration of shared data and folders from Google Disk to SharePoint Online (file storage) and adaptation of data work through MS Teams. Transfer of domain names. Training program for company employees and technical specialists.
Implementation period: 3 months.
Results: Transfer of all mail, including contacts and personal calendars of all employees from Gmail to Exchange Online, transfer of personal data from Google Disk to OneDrive, migration of shared data and folders from Google Disk to SharePoint Online (file storage) and adaptation of data work through MS Teams. Transfer of domain names. Training program for company employees and technical specialists.
On-prem servers (Windows, Linux) migration to Azure
The task: Due to the expiration of the extended warranty and the expiring physical servers in the local data center, the customer decided to partially transfer their computing power to the Azure cloud.
Source data: Manufacturing company, textile industry. Local virtualization platform - VMware. More than 80 servers that are remotely accessed from various regions. Different OS types - Windows Server 2003-2016, Linux (Debian, Ubuntu).
Implementation period: 3 months.
Results: A full audit of the current infrastructure for compatibility with the Azure cloud platform was completed. A hybrid network topology was created with separate AD sites in the cloud connected via Express Route. 60+ servers were migrated and put into operation, including application servers, database servers (MS SQL, MySQL), and terminal access servers. Some of the database servers were converted to SaaS model. The remaining servers in the on-prem data center retained their current location, as cloud environments are not.
Implementation period: 3 months.
Results: A full audit of the current infrastructure for compatibility with the Azure cloud platform was completed. A hybrid network topology was created with separate AD sites in the cloud connected via Express Route. 60+ servers were migrated and put into operation, including application servers, database servers (MS SQL, MySQL), and terminal access servers. Some of the database servers were converted to SaaS model. The remaining servers in the on-prem data center retained their current location, as cloud environments are not.
Building a hybrid infrastructure
The task is the implementation of a new ERP solution in the company.
Source data: Trading company with 100+ employees who need access to the new ERP 24/7. Outdated and insufficient computing power on local servers.
Implementation period: 1 month.
Results: Designing and implementing a hybrid network topology with its expansion into the Azure cloud environment using VPN tunnels, creating individual sites within AD/ ADDS. Deployment and configuration of virtual machines for ERP application and Microsoft SQL Server databases. Configuration of disaster recovery using Azure Site Recovery tools.
Implementation period: 1 month.
Results: Designing and implementing a hybrid network topology with its expansion into the Azure cloud environment using VPN tunnels, creating individual sites within AD/ ADDS. Deployment and configuration of virtual machines for ERP application and Microsoft SQL Server databases. Configuration of disaster recovery using Azure Site Recovery tools.
Building an application architecture for operation in the Azure cloud environment
The task is to develop an application architecture adapted for operation in the Azure cloud environment, complying with GDPR and HIPAA standards and regulations.
Source data: Startup in the HR solutions segment. Initial development was carried out on local servers. Applied technologies in development - Node.js, Angular, MySQL, Elastic.
Implementation period: 4 months.
Results: Audit of the current state of the solution. An architecture has been designed that could form the basis for the technical implementation of GDPR and HIPPA compliance. Recommendations have been provided to developers for the refinement and optimization of code for operation in the Azure cloud environment. Environments have been deployed for development, testing, and production. IaC approaches have been applied for the further implementation of DevOps methodologies. Solutions have been built using services: Azure App Services, MySQL instances, VM, VNet, Blob storage, Cosmos DB, Elastic Stack, Azure WAF, Azure CDN, Docker, Key vault, Cloudflare.
Implementation period: 4 months.
Results: Audit of the current state of the solution. An architecture has been designed that could form the basis for the technical implementation of GDPR and HIPPA compliance. Recommendations have been provided to developers for the refinement and optimization of code for operation in the Azure cloud environment. Environments have been deployed for development, testing, and production. IaC approaches have been applied for the further implementation of DevOps methodologies. Solutions have been built using services: Azure App Services, MySQL instances, VM, VNet, Blob storage, Cosmos DB, Elastic Stack, Azure WAF, Azure CDN, Docker, Key vault, Cloudflare.
Configuring DevOps processes and development environments (CI/CD, Docker, App Service, Databases)
The task is the introduction and maintenance of DevOps processes within the existing solution, increasing the security parameters of the entire solution as a whole.
Source data: Several environments have been deployed and used in Azure for development and testing. All work and processes are performed through the GUI. Access to all services is carried out through public connection interfaces. Lack of production environment for launching the project. Multiplicity of users with privileged access (global admin).
Implementation period: 6 months+.
Results: A complete audit of the developed application was carried out. The service structure was revised and a new solution diagram was presented that meets all CAF/WAF principles for building a solution in the Azure environment. Public connections were closed, Private Endpoints were introduced, VNets were reconfigured, a NAT was connected, all internal communications for applications and databases were launched.
Implementation period: 6 months+.
Results: A complete audit of the developed application was carried out. The service structure was revised and a new solution diagram was presented that meets all CAF/WAF principles for building a solution in the Azure environment. Public connections were closed, Private Endpoints were introduced, VNets were reconfigured, a NAT was connected, all internal communications for applications and databases were launched.
Building an architecture for VDI based on Azure Virtual Desktop
The task is moving all users to a single VDI environment (Azure Virtual Desktop) due to distributed environments in different clouds and local data centers. Integration into corporate AD with application of all GPOs at the enterprise level.
Source data: 900+ users who work around the world in different time zones.
Implementation period: 4 months.
Results: Initial infrastructure audit, analysis of applications with which users work, and their segmentation into groups. Designing a hybrid AD/ADDS topology using Azure VPN. Launch of a pilot project for the selected user group and testing for 1 month. Connecting all public resources - shared folders, printers, scanners. Deployment of 5 pools (groups) adapted to various tasks and applications involved in work. Configuration of maintenance plans and backup. Training of IT staff on working with the new environment, transfer of documentation.
Implementation period: 4 months.
Results: Initial infrastructure audit, analysis of applications with which users work, and their segmentation into groups. Designing a hybrid AD/ADDS topology using Azure VPN. Launch of a pilot project for the selected user group and testing for 1 month. Connecting all public resources - shared folders, printers, scanners. Deployment of 5 pools (groups) adapted to various tasks and applications involved in work. Configuration of maintenance plans and backup. Training of IT staff on working with the new environment, transfer of documentation.