In 2025, Microsoft will implement significant changes to its Remote Desktop Protocol (RDP) ecosystem, with a particular focus on the deprecation of the Remote Desktop client (Microsoft Store version) and the transition to other solutions. As RDP plays a crucial role in enterprise IT environments, administrators must prepare for these changes to maintain secure and efficient remote access to critical resources. Below is a comprehensive overview of what administrators need to know, with a technical focus on migrating away from legacy solutions.

End of Support for Remote Desktop App (Microsoft Store Version)

Effective May 27, 2025, Microsoft will officially discontinue the Remote Desktop app from the Microsoft Store. This app, which has served as the main method for Windows clients to connect to remote desktops, will no longer be supported for remote access to services such as Azure Virtual Desktop (AVD), Windows 365, and Microsoft Dev Box.

From a technical standpoint, administrators must ensure that users who rely on this app transition to an alternative solution before support ends. The Remote Desktop app has several limitations, including:

• Dependency on the Microsoft Store and lack of advanced customization capabilities for enterprise use.

• Incompatibility with custom configurations such as custom Group Policies or RDP settings at the enterprise level.

To facilitate a smooth transition, Microsoft recommends moving users to the Windows App for accessing RDP-based services. This solution integrates better into enterprise ecosystems and offers the following advantages:

1. Centralized Management via Microsoft Endpoint Manager (Intune):

   • The Windows App can be centrally managed via Intune, allowing for deployment and policy enforcement at scale.

   • Administrators can configure device redirection policies and enforce RDP security configurations at a granular level using Mobile Device Management (MDM) and Mobile Application Management (MAM).

2. Enhanced Security and Compliance:

   • The Windows App supports Windows Hello for Business authentication and Multi-Factor Authentication (MFA), improving security during remote access sessions.

   • It integrates seamlessly with Azure Active Directory (Azure AD) for seamless user provisioning and identity management.

   • Administrators can apply conditional access policies to ensure only compliant devices can initiate remote desktop sessions.

3. Advanced Networking Features:

   • The Windows App supports automatic VPN detection and direct routing for secure connectivity.

   • It integrates WAN optimization features, improving remote session performance over fluctuating network conditions.

4. Customizable Deployment Options:

   • Windows App supports configurations for custom RDP file settings, allowing for more flexibility in deployment across different user groups or organizational departments.

   • Integration with Azure Virtual Desktop (AVD) and Windows 365 enables simplified session launching, reducing the need for manual configuration of RDP settings.

End of Support for Remote Desktop Client (MSI Version)

In addition to the Microsoft Store version, the standalone Remote Desktop client for Windows (MSI) will be deprecated as of March 27, 2026. While this client is still in use across many enterprises, its eventual obsolescence requires careful planning for a migration strategy. Key technical considerations include:

• Deprecation of Support for Legacy RDP Protocols:

  • Organizations using custom RDP configurations tied to the MSI version must update their deployments to the Windows App or other Microsoft-supported RDP solutions.

  • Any use of custom RDP file configurations will need to be migrated or reconfigured in the new app.

• Compatibility Testing:

  • For organizations that leverage the MSI RDP client with third-party RDP servers or custom load balancing configurations, comprehensive testing is required to ensure full compatibility with the Windows App.

  • Testing should include performance analysis, network load distribution, and failover mechanisms.

Traditional RDP (MSTSC) Support Continues

The legacy Remote Desktop Connection (MSTSC) tool will remain supported beyond 2025 and will continue to be a viable method for connecting to Windows servers or other RDP-enabled systems in environments where more complex configurations are unnecessary. However, MSTSC lacks the management and security benefits that come with the Windows App and Intune integration.

For enterprises relying on on-premises RDP servers or systems that do not yet use cloud-based solutions (such as Azure Virtual Desktop), MSTSC may still be the preferred option for basic RDP connectivity.

Action Steps for Administrators: A Detailed Technical Migration Guide

1. Assess Existing RDP Infrastructure:

   • Identify all systems using the Microsoft Store app and the MSI client for remote access, including server configurations and VPNs.

   • Evaluate the network configurations, authentication requirements, and third-party integrations that will be impacted by the deprecation of the Microsoft Store app.

2. Plan Transition to the Windows App:

   • Roll out the Windows App using Microsoft Endpoint Manager (Intune) for streamlined deployment and policy management.

   • Configure RDP settings, including device redirection, audio/video settings, and resource sharing policies via Intune to ensure compatibility with organizational requirements.

3. Test Compatibility and Performance:

   • Perform pilot migrations with a small group of users, testing network latency, VPN performance, and resource access under real-world conditions.

   • Test compatibility with applications that rely on RDP for remote access, ensuring that custom configurations (such as session broker configurations or multi-session handling) are supported in the new app.

4. Configure Centralized Security Controls:

   • Implement conditional access policies to restrict remote desktop access to compliant devices.

   • Enable Microsoft Defender for Endpoint for device protection and integrate with Microsoft Sentinel for continuous security monitoring of RDP connections.

5. Migrate Users and Monitor Usage:

   • Migrate users in phases to reduce service disruption. Provide training and support resources to ensure a smooth transition.

   • Continuously monitor the performance and security of the migration process using Microsoft 365 Admin Center and Azure AD logs.

6. Decommission Legacy RDP Clients:

   • Once the migration is complete, decommission legacy MSI RDP clients and Microsoft Store app installations.

   • Archive any data associated with legacy RDP solutions for compliance or future auditing requirements.

[mai mult...]

As Microsoft officially ends support for Skype in 2025, Microsoft Teams has become the go-to platform for communication and collaboration within businesses. Migrating from Skype to Teams, particularly in larger organizations, requires careful planning, configuration, and execution. This guide will walk through the essential steps and technical considerations for administrators in the migration process.

While Skype revolutionized real-time communication, it lacks some critical features required by modern businesses. Microsoft Teams extends beyond chat and calling; it is an all-in-one collaboration suite that integrates with Microsoft 365 applications, including SharePoint, OneDrive, and Outlook. Teams also provides robust enterprise security and compliance capabilities, making it the ideal successor to Skype.

Additionally, Skype for Business is being phased out, and Microsoft Teams now supports business-critical functionalities such as:

• VoIP calling

• Meetings and video conferencing

• Advanced file sharing and collaboration

• Tight integration with the Microsoft 365 ecosystem

Steps for Migrating from Skype to Microsoft Teams

1. Preparation and Assessment

Before starting the migration, a comprehensive Skype usage assessment should be conducted. Administrators need to identify the features being used, such as:

• Chat and messaging

• VoIP calling and conferencing

• Presence information

• Screen sharing and file sharing

Once this assessment is done, the next step is to determine the necessary Teams configurations that will meet these needs. It’s also crucial to ensure that the Teams licensing aligns with your organization’s requirements, as different Teams plans offer varying levels of access to features like calling, meetings, and collaboration.

2. Teams Configuration

To configure Microsoft Teams for your organization, you must enable Teams in the Microsoft 365 Admin Center and set it as the default communication platform. This involves:

• Configuring Teams policies for messaging, meetings, and calling.

• Enabling features such as Teams Calling Plan, Direct Routing, or Operator Connect for VoIP services.

• Setting up Security & Compliance Center policies for data retention, eDiscovery, and legal hold for Teams communications.

• Integrating Azure Active Directory to manage user authentication and access to Teams resources.

For organizations that previously relied on Skype for Business, you’ll need to manage coexistence modes, which dictate how Skype and Teams will interact during the transition. The coexistence modes include:

• Islands Mode: Skype and Teams operate independently.

• Teams-Only Mode: All communication occurs exclusively through Teams.

• Skype for Business-Only Mode: Skype is the primary platform, with Teams disabled.

3. User Migration and Transition

Once Teams is configured, it’s time to start the migration of users and data. Microsoft offers Skype to Teams Migration PowerShell Scripts and the Microsoft Teams Upgrade PowerShell Module to help automate the migration process. Key tasks during the migration include:

• Migrating user chat history from Skype to Teams

• Migrating users from Skype for Business Online to Teams

• Ensuring all user profiles are updated in Active Directory

• Transferring group chats, scheduled meetings, and file shares.

A phased migration approach is often recommended, where users can operate both Skype and Teams simultaneously (using Teams Only or Skype for Business modes) until all users are transitioned.

4. Configuring Teams Calling

If your organization relies on Skype for Business calling features (e.g., PSTN calls, voicemail, etc.), you will need to configure Teams to support Teams Calling Plans, Direct Routing, or Operator Connect. This involves:

• Purchasing and assigning Teams Calling Licenses for users who require external calling.

• Setting up Direct Routing with a Session Border Controller (SBC) if you’re using your own telephony infrastructure.

• Configuring Teams Calling Policies for call forwarding, voicemail settings, and emergency calling.

5. User Training and Adoption

User adoption is critical for the success of the migration. Administrators must ensure that training materials and resources are available for end users to get acquainted with Teams. Microsoft offers Teams Training and Adoption Guides that can help users transition seamlessly. Key features to train users on include:

• Navigating the Teams interface for chat, meetings, and file sharing

• Understanding the difference between Channels, Teams, and Private Chats

• Configuring Teams notifications and managing user presence

• Sharing files and collaborating using OneDrive and SharePoint within Teams.

6. Testing and Validation

Before completing the migration, it is crucial to test key functionalities, including:

• Call quality and reliability for VoIP and video conferencing

• Message and file synchronization between Skype and Teams

• Meeting scheduling and calendar integration with Outlook

• Compliance and security controls to ensure data protection policies are met.

Testing should be done with a small group of users first, to identify any issues before rolling out Teams organization-wide.

7. Decommissioning Skype

Once Teams has been fully implemented, and all users have transitioned, you can begin the process of decommissioning Skype. This includes:

• Disabling Skype for Business services

• Archiving Skype data according to company compliance policies

• Ensuring that users no longer rely on Skype for communication and collaboration.

Key Technical Considerations for Admins

• License Management: Ensure the correct Microsoft 365 licenses are assigned to users based on the features they require (e.g., Teams Calling Plans, Office 365, Enterprise Mobility + Security).

• Bandwidth Requirements: Teams calls and video conferencing may require significant bandwidth, especially with larger teams. Ensure your network infrastructure is prepared to handle Teams traffic.

• End-User Experience: Teams offers a richer collaboration experience than Skype. It’s crucial to monitor the end-user experience and optimize configurations for performance and usability.

• Compliance and Security: Teams offers advanced compliance features like information barriers, retention policies, and legal hold. Make sure these are configured according to your organization’s compliance needs.

[mai mult...]

Skype revolutionized the way people connected across the globe, offering free video and voice calls long before Zoom or WhatsApp became mainstream. In its prime, “Skype” was a verb. However, in recent years, Skype lost market share to faster, more integrated platforms. Microsoft has gradually been phasing out Skype in favor of Microsoft Teams, especially in the business and education sectors. Today marks the official end of that transition.

What happens to user accounts?

Users are encouraged to export their chat history and data before the service becomes inaccessible. Microsoft recommends switching to Teams, which now supports both business and personal communication.

[mai mult...]