Support walkthrough 01
Azure Virtual Desktop support
Supporting enterprise virtual desktops from sign-in to session performance, with checks across Entra ID, session hosts, FSLogix and storage.
Infrastructure Engineer · Azure & Windows
From the first incident report
to a working system.
Cloud Support Engineer at TCS since March 2024. I investigate L2 incidents across Azure, Windows and virtual desktops, verify recovery, and leave a clear handover.
Discuss a roleUnderstand the environment.
Virtual machines, storage, and network dependencies. I connect the symptoms to the system behind them.
Explore the expertiseEnterprise cloud support
TCS · Cloud Support Engineer · March 2024 to present
Azure Administrator Associate
Microsoft certified · VerifyDevOps Engineer Expert
Microsoft certified · VerifyExperience in practice
Two areas of my work at TCS, with the checks, decisions and handover behind them. These walkthroughs explain how I investigate a problem and verify that service is restored.
View my full experienceSupport walkthrough 01
Supporting enterprise virtual desktops from sign-in to session performance, with checks across Entra ID, session hosts, FSLogix and storage.
Support walkthrough 02
Keeping Azure resources and release activity connected, so infrastructure and application teams have the evidence they need when a deployment or service needs attention.
What I work on
AVD sessions, FSLogix profiles, and the checks that get a desktop working again.
Read moreEntra ID, user access, and authentication. Finding where the sign-in path breaks.
Read moreAzure VMs, storage, and Windows systems. Connecting the symptoms to the platform.
Read moreL2 troubleshooting, clear escalations, and PowerShell for work that keeps coming back.
Read moreFrom my notebook
An AVD sign-in failure can begin in identity, brokering, the client, a session host, the network, or FSLogix. I use the failed stage and its evidence to choose the smallest safe next check.
When FSLogix fails, I classify the symptom, preserve the profile logs, and follow the evidence across sessions, hosts, policy, SMB storage, permissions, and the container before changing user data.
Open to the right next role
Looking for someone who understands Azure, Windows, and the reality of support work? I'd like to hear what you're building.