VIRTUAL DESKTOPS AND REMOTE APPS

Azure Virtual Desktop Deployment and Management

Run Windows desktops and business applications centrally in Microsoft Azure. Mica IT determines which AVD configuration is truly necessary for each user group and then handles the migration, security, monitoring, and support.

  • Full desktop, shared workspace, or applications only
  • Migration from RDS, Citrix, or an existing AVD environment
  • Ongoing management, cost monitoring, and support provided by Mica IT
Schedule an AVD scan
Find out when AVD is a good fit
Azure Virtual Desktop - Mica IT

Not every workplace needs to be entirely virtual

For many employees, a managed laptop with Microsoft 365 and Intune is the simplest solution. Azure Virtual Desktop becomes an attractive option when Windows applications need to run centrally, users in different locations need the same environment, or computing power and data need to remain together for specific reasons.
  • Applications and user profiles are centrally configured
  • Capacity tailored to actual usage
  • Existing software and peripherals have been tested in advance
  • Management and user support provided by a single IT team

When Azure Virtual Desktop Really Adds Value

AVD is not the default choice for every employee. The solution is particularly effective when centralization, flexibility, or specialized applications provide a clear rationale for its use.

Replacing RDS or Citrix

Is the existing central workspace due for an upgrade? We're investigating which components can be migrated to Azure and which dependencies need to be resolved first. 

Centralized Delivery of Business Applications

ERP, accounting software, or other Windows applications are published centrally, without requiring a full installation on each individual device.                                                             

Keeping Applications and Data Together

Applications that rely on databases or files can perform better when processing, connections, and data are designed as a single environment.

External and temporary users

Grant specific users controlled access only to the desktop or applications they need for their work.

Allowing capacity to adjust dynamically

Adjust shared capacity to match working hours and usage, so that the system does not have to constantly operate at maximum peak capacity.

Specialized Computing Power

Provide selected users with additional processor capacity, memory, or GPU computing power after the application has been tested from both a technical and financial perspective.

Is Azure Virtual Desktop a good fit for your organization?

We’ll assess your applications, users, connections, and current environment. You’ll receive honest advice on AVD, the Modern Workplace, or a combination of both.

Schedule an AVD scan

The Right AVD Type for Each User Group

We do not place every employee in the same virtual environment. For each role, we choose the simplest configuration that meets the requirements for applications, performance, security, and cost.

The application only — RemoteApp

The employee only opens the centrally hosted application. All other work continues to take place on the regular managed workstation.

Shared desktop — pooled

Multiple users share the available capacity. Each user is assigned their own profile, permissions, and applications.

Personal desktop — personal

A user is assigned their own virtual machine when performance, isolation, or a specific configuration requires it.

What Customers Say About Centralized Workstations and Support from Mica IT

A virtual workplace is only valuable if applications continue to function properly and employees receive prompt assistance. Read about how customers experience Mica IT’s technical expertise, direct communication, and support.

Here's how Mica IT implements Azure Virtual Desktop

We first conduct small-scale testing and only roll out further once applications, performance, access, and support processes have been sufficiently validated.

Step 1. Identify users and applications

We assess functions, applications, data, integrations, peripherals, locations, peak usage, and the current RDS, Citrix, or desktop environment.

Step 2. Determine Feasibility and Costs

We assess application compatibility, Microsoft licenses, connections, user profiles, and expected Azure usage.

Step 3. Designing the Architecture and Security

We design identity, networking, host pools, user profiles, images, access, monitoring, and the distribution of responsibilities.

Step 4. Build the environment and conduct a pilot

A representative user group tests applications, printing, scanners, audio, video, peripherals, and day-to-day performance.

Step 5. Migrate and Publish Applications

We will migrate the agreed-upon profiles, data, and applications, and deploy either full desktops or only the necessary RemoteApps.

Step 6. Phased Rollout and Support

Users transition in controlled groups and receive clear explanations and support regarding the new workflow.

Step 7. Manage and Optimize

Mica IT manages images, updates, applications, capacity, user profiles, performance, incidents, Azure costs, and day-to-day support.

Ready for a manageable AVD environment?

Mica IT creates a concrete plan for the right users, applications, and capacity. You’ll see in advance how implementation, management, and Azure costs are structured.
Request an AVD proposal

Frequently asked questions about Azure Virtual Desktop

Azure Virtual Desktop is Microsoft's platform for centrally delivering full Windows desktops and individual Windows applications from Azure.

Microsoft manages the central connectivity and platform services. Mica IT designs and manages the customer-specific environment, including virtual machines, host pools, images, user profiles, applications, networking, access, monitoring, and support.

Employees connect via the Windows app or a supported web environment and are presented with the desktop or applications assigned to them.

In the Modern Workplace, employees typically work on a locally managed laptop. Microsoft 365, Intune, security, backup, and support are provided as a single service.

With Azure Virtual Desktop, the entire Windows desktop or a specific application runs centrally in Azure. The employee's device remotely displays what is running in Azure.

Many organizations use both approaches. In such cases, most employees work in a standard Modern Workplace, while specific users or applications are delivered via AVD.

No. AVD is often most useful for a specific user group or a number of business applications.

For example, an employee can:

  • use only one central application via RemoteApp;
  • working on a shared virtual desktop;
  • get a personal virtual desktop;
  • Continue to work entirely locally on a managed laptop.

Mica IT makes this decision on a per-user-profile basis. This helps us prevent the environment from becoming larger, more complex, and more expensive than necessary.

Yes. With RemoteApp, a centrally installed application can be made available to a specific user. The application then appears through the Windows App without the user having to open the entire virtual desktop.

This is useful, for example, for accounting software, an ERP system, an older Windows application, or an application that needs to run close to a central database.

Beforehand, we test, among other things, the integrations, license terms, printers, scanners, file paths, and other technical dependencies.

Many Windows applications can run within an AVD, but this should not be assumed without further investigation.

Among other things, we check:

  • support for the Windows operating system in use;
  • ability to support multiple concurrent users;
  • the supplier's license terms;
  • dependencies on databases and file servers;
  • printing, scanning, and USB devices;
  • audio, video, and video calls;
  • required processor, memory, or GPU capacity;
  • integrations with other applications.

That is why, before the full rollout, we are conducting a pilot with a representative group of users and real-world tasks.

Yes. However, a migration isn't always a direct copy of the existing environment.

First, we take stock of the applications, images, user profiles, databases, file storage, printing services, identity management, network connections, and security settings. Then, we determine which components can be migrated, replaced, or simplified.

The new environment will be tested with a pilot group and then rolled out in phases. This will help us minimize disruption and prevent outdated configurations from being unnecessarily migrated to Azure.

No. Azure Virtual Desktop offers many options for centralized security, but the ultimate level of security depends on the configuration and day-to-day management.

Depending on the risks and licenses, we set up, among other things:

  • multi-factor authentication;
  • Microsoft Entra Conditional Access;
  • minimal administrative privileges;
  • network security;
  • endpoint security;
  • update and image management;
  • logging and monitoring;
  • restrictions on clipboard, disk, and device redirection;
  • Appropriate access for external users.

Mica IT’s management processes are ISO 27001:2022-certified. This does not mean that every risk is eliminated, but it does mean that security is addressed in a structured and risk-based manner.

The user experience depends on several factors:

  • the internet connection and latency;
  • the location of applications and data;
  • the selected virtual machines;
  • the number of concurrent users;
  • the setup of user profiles;
  • the applications and peripheral devices;
  • the network configuration;
  • the user's local equipment.

We therefore do not make a general promise that every application will always run quickly. During the pilot, we will monitor day-to-day operations, and after the system goes live, we will continue to track performance, capacity, and user experience.

Not automatically.

The central AVD platform services and virtual desktops run on Microsoft Azure. However, applications, databases, files, identities, or other technical dependencies may still reside in an on-premises environment or another data center.

Mica IT evaluates each component to determine whether it makes sense to retain it, connect it via a secure connection, or migrate it to Azure. The appropriate solution may be fully cloud-based, hybrid, or phased.

The total costs may include:

  • appropriate Microsoft or Windows user licenses;
  • virtual machines and computing power in Azure;
  • profile and other storage;
  • network traffic and network services;
  • logging and monitoring;
  • additional security services;
  • setup or migration;
  • administration and user support.

Shared desktops, autoscaling, usage schedules, and appropriate Azure reservations can help control costs. However, AVD isn't automatically cheaper than an on-premises workstation or Windows 365 in every situation.

After the assessment, you will receive a transparent breakdown of costs, including the basic principles, expected Azure usage, project costs, and ongoing management.

At its core, Windows 365 provides users with a personal cloud PC. The capacity is tied to the selected license, and each user has their own virtual computer.

Azure Virtual Desktop offers more flexibility in terms of technical configuration. You can work with:

  • shared desktops for multiple users;
  • personal desktops;
  • only centrally published applications;
  • different capacities per user group;
  • Azure usage that can adapt to usage and planning.

Windows 365 may be a simpler and more predictable option for a personal Cloud PC. AVD may be a better fit when shared capacity, RemoteApps, customization, or integration with an existing Azure environment is required.

Mica IT compares both options based on users, applications, management needs, and total costs.

Yes. Mica IT can handle all day-to-day management or work in collaboration with your in-house IT staff or IT department.

Depending on the terms of our agreement, we manage, among other things:

  • session hosts and host pools;
  • images and Windows updates;
  • applications and RemoteApps;
  • user profiles;
  • capacity and autoscaling;
  • monitoring and malfunctions;
  • performance;
  • Azure costs;
  • user support;
  • changes and new users.

The scope, responsibilities, support hours, and exceptions are clearly defined in advance.