Microsoft Azure & Metaswitch Cuts: Impact On Network Operators

How Will Microsoft’s Azure and Metaswitch Cuts Impact Network Operators? According to industry reports, Microsoft is set to reduce its Azure for Operators and Mission Engineering Units by 1,500 jobs. How will this influence Microsoft’s commitment to the telecom industry? What does this mean for Azure-based migrations? Telecom abhors a vacuum – which telecom software development services will emerge as a credible alternative to Metaswitch? Read on to find out.

@GREG GOODWIN, Software Mind

Microsoft Disinvests In Metaswitch

Microsoft’s purchase of the UK-based Metaswitch in 2020, for a reported $270 million USD, was supposed to boost the tech giant’s presence in the telecommunications world. Metaswitch had built a successful reputation as a pioneering cloud native network software provider and was highly sought after for its voice-based communications technologies like private branch exchange (PBX). In 2020, Microsoft also acquired another development company – Affirmed Networks – primarily because it could produce core software for 5G networks. For Microsoft, these acquisitions would strengthen their telecom portfolio and make them an attractive option for operators around the world.

A mere four years later, the situation looks different. Though it’s early days, all signs indicate that either Metaswitch or Affirmed's assets will be sold off or vanish from the market. But, while Microsoft’s disinvestment in a key element of their telecom offer may be a bit of a surprise, it does not signal a complete withdrawal from the industry.

Microsoft is still dedicated to providing Azure for telecom operators and is keen to integrate AI developments into telecommunications. Microsoft wants to provide the infrastructure but not the network functions (applications) that may distinguish one provider from another. It seems the main priority for Microsoft going forward is to entice Tier 1 customers into moving their infrastructures to the cloud. While increasing numbers of operators are moving to cloud-based solutions, migration to any platform carries risks that need to be carefully assessed. However, the negative consequences that come from not migrating to a new platform should also be clearly understood.

The Risks Of Using Software That May Lose Support

In a highly regulated market that also has disparate legal requirements, staying compliant can be a challenging task. Not updating existing systems or failing to develop evolutive software increases the chances of not keeping up with dynamically changing laws. This is especially true considering the immense opportunities that AI, cloud and data engineering present to telecom providers.

Beyond the dangers of litigation (and the inevitable financial and reputational harm), operators face pressure to deliver solutions that not only attract customers but retain them. This is especially true in the telecommunications world, where customer experience (CX) depends on intuitive design and functionality, dependable coverage, impressive speed, and easy access – all while being assured the highest security. With ever-increasing competition, failure to upgrade is akin to surrendering a huge part of your existing customer base while signaling a lack of interest in gaining new ones.

What Does It Mean For Azure-Based Migrations?

Azure-based migrations might experience several impacts. With a reduced workforce in Microsoft's Azure for Operators and Mission Engineering Units, network operators could face longer migration timelines, as fewer experts may be available to provide tailored support during the transition.

This scenario may require operators to engage in more detailed planning and risk assessments to ensure their migration strategies align with evolving service levels. Additionally, operators might need to explore alternative support structures—such as partnering with specialized migration consultants or leveraging third-party expertise—to fill any gaps in technical assistance or innovation.

Ultimately, while the overall migration to Azure remains attractive, operators should prepare for potential short-term challenges and adjust their strategies accordingly.

Telecom Operators: 10 Steps For A Successful Migration

Given the uncertain future of Metaswitch, network operators may be considering migrating to a new platform that can offer long-term stability, robust security, and flexible scalability – especially in terms of designing and developing new features and functionalities. This applies to operators who have relied on Metaswitch as well as those who have depended on OpenCloudRhino (acquired by Metaswitch in 2017,) which is an application server that supports the development of telecommunications applications. For both, Software Mind can provide alternatives and help with migrations. While any migration should be customized to an operator’s specific needs and goals, an effective process should contain the following ten steps.

1. Assess The Need For Migration

Identifying reasons for migration (e.g., cost, scalability, features), evaluating current platform limitations, setting migration goals and objectives.

2. Plan The Migration

Creating a migration team, defining the scope, developing a timeline and budget, conducting a risk assessment.

3. Choose A New Platform

Establish criteria for selecting a new platform, comparing available alternatives (features, costs, support), making a final selection.

4. Prepare For Migration

Conducting a thorough audit of the current system, documenting existing configurations and workflows, backing up all data and settings, training the team on the new platform.

5. Extract Data From The Metaswitch Platform

Cleaning and validating data, importing data into the new platform, ensuring data integrity and consistency.

6. Configure The New Platform

Setting up the new platform environment, replicating existing configurations, customizing features and settings as needed, integrating with existing systems and third-party applications.

7. Test & Validate

Developing a comprehensive testing plan, conducting functional and performance testing, addressing any issues or discrepancies, validating the new platform’s readiness for production.

8. Train & Support

Providing training for end-users and administrators, creating user manuals and support documentation, establishing support channels and resources.

9. Perform Migration

Scheduling the migration date and time, communicating the migration plan to all stakeholders, launching the migration during a low-usage period, monitoring the migration process, and addressing issues in real-time.

10. Post-migration Activities

Conducting a post-migration review, ensuring all services are running smoothly, making necessary adjustments and optimizations.

Software Mind has carried out multiple Virtual PBX system migrations, as well as migrations for numerous other telecommunications platforms. One recent migration project was a Virtual PBX platform for a Tier-1 mobile operator. The last phase of the migration was carried out in Q1 this year – the project covered migrations of user profiles and services data in BroadWorks, HSS, DNS, and the bespoke Recorder application. A total of 61 services, 2800 groups, and 25 thousand subscribers were migrated in the project. With over 65 million user and service profiles migrated over the years throughout various projects across platforms like VPBX, Voicemail, and IDM, Software Mind has developed a framework approach for the migration process.

Of course, the primary job of any technical partner is to tailor processes to individual company requirements, so while the aforementioned steps are a proven strategy, there could be variations depending on the exact scope of a migration. However, even though there will be different technical specifications for each migration, there are common obstacles that need to be overcome.

6 Major Challenges For Operators Undertaking A Migration

Data Integrity & Accuracy

Ensuring data is transferred without corruption or loss of material while consistently mapping and maintaining data between the old and new systems.

Downtime & Business Continuity

Minimizing downtime during a migration process to prevent business disruption planning for backup and recovery scenarios.

Compatibility

Detecting and addressing potential variances early in the process.

Security Risks

Protecting sensitive data during the transfer process and running security checks before and after a migration.

User Adoption & Training

Educating staff to ensure efficient use of the new system.

Post-migration Support

Getting ongoing support that includes maintenance of existing systems and development of new ones.

Network Operators Need Services & Consultancy

Undoubtedly, the integration of new tools and technologies within the telecom industry is creating challenges and opportunities for network providers. To overcome obstacles in upgrading offers, operators understand the urgency of carrying out a migration – this article has outlined the risks and rewards of such an initiative. While navigating a migration can be a daunting task, an experienced technology partner can make the process seamless, tailor a migration to business needs, and control costs in a way that maximizes resources and drives innovation. That’s why telecom leaders around the world turn to Software Mind, a technology partner that has been supporting the telecom industry for over 25 years.

Software Mind has telco expertise that supports clients. If you’re looking to migrate your platform, create robust new functionalities, maximize 5G and AI solutions, deliver an enhanced user experience, and generate a new revenue stream, the Software Mind team is ready to help. Get in touch with our experts and learn how they can support your growth goals by filling out this form.

Visit https://softwaremind.com/