# Sai Prasanna Surisetty: professional profile and technical writing Source: https://www.prasannasurisetty.com/ Profile updated: 2026-09-08 ## Professional profile At TCS, I support Azure and Windows environments used by enterprise teams. My day-to-day work covers virtual desktops, identity and L2 incidents: finding the cause, restoring service and checking that the fix holds. I use monitoring data, PowerShell and clear handover notes to make the next incident easier to resolve. - Professional focus: Infrastructure Engineer | Azure, Windows & L2 Operations - Current employment: Cloud Support Engineer at Tata Consultancy Services (TCS) - Based in: Hyderabad, India - Career interest: I'm interested in infrastructure, Azure support and L2 systems roles with teams worldwide, where I can help keep services reliable and solve the problems behind an incident. - Roles of interest: Infrastructure Engineer; L2 Systems Engineer; Cloud Support Engineer; Azure Support Engineer; Azure Virtual Desktop Support Engineer; Cloud Operations Engineer - Opportunity details: Role location, work eligibility and start dates can be discussed directly for each opportunity. - Profile: https://www.prasannasurisetty.com/about - Resume: https://www.prasannasurisetty.com/resume - Contact: https://www.prasannasurisetty.com/contact - LinkedIn: https://www.linkedin.com/in/sai-prasanna-surisetty/ - Email: contact@prasannasurisetty.com ## Employment ### Cloud Support Engineer, Tata Consultancy Services (TCS) March 2024 to present | Hyderabad, India Source: https://www.prasannasurisetty.com/experience - Provide L2 support for enterprise users, investigating system, access, authentication, connectivity and performance incidents - Support Azure Virtual Desktop across host pools, session hosts, application groups, user assignments, and FSLogix profiles - Investigate AVD sign-in failures, temporary profiles and slow sessions using platform logs and monitoring data - Administer Microsoft Entra ID through user provisioning, group management, RBAC, MFA, and Conditional Access support - Manage Azure virtual machines and storage, using Azure Monitor and Log Analytics to investigate infrastructure health - Manage incidents against SLAs, record root causes and resolutions, and coordinate complex escalations with global engineering teams - Automate recurring support tasks with PowerShell and write runbooks that make troubleshooting and handover easier - Support Azure DevOps deployment and release activities alongside broader infrastructure and application support ## Areas of expertise ### Azure Virtual Desktop and FSLogix Getting people into their desktops and keeping sessions usable, with checks from identity and assignment through to hosts, profiles and storage. Source: https://www.prasannasurisetty.com/expertise#azure-virtual-desktop - Support host pools, session hosts, application groups, user assignments, and day-to-day AVD operations - Investigate failed sign-ins, profile errors, disconnected sessions and slow desktops - Check FSLogix profile attachment alongside storage access, permissions, session state and logs Systems: Azure Virtual Desktop, FSLogix, Host Pools, Session Hosts, Application Groups, Azure Monitor. ### Microsoft Entra ID and access support Helping users reach the right resources by tracing access issues through accounts, groups, permissions and sign-in controls. Source: https://www.prasannasurisetty.com/expertise#identity-access - Support user provisioning, group management, RBAC, MFA, and Conditional Access operations - Trace access and authentication failures before changing permissions or escalating the incident - Record the access checks, approved changes and verification so another engineer can follow the work Systems: Microsoft Entra ID, RBAC, MFA, Conditional Access, Azure Key Vault, User Provisioning. ### Azure and Windows operations Supporting the virtual machines, storage, Windows systems and network connections behind everyday enterprise services. Source: https://www.prasannasurisetty.com/expertise#azure-windows-operations - Administer and support Azure virtual machines, storage, resource groups, and core networking components - Use Azure Monitor and Log Analytics to investigate resource health and service problems - Troubleshoot Windows access, authentication, applications and connectivity, checking the simplest causes first Systems: Azure VMs, Azure Storage, Windows Server, Log Analytics, Virtual Networks, Network Security Groups. ### L2 incident response and automation Following an incident through to recovery, keeping the handover clear and turning repeat fixes into useful scripts and runbooks. Source: https://www.prasannasurisetty.com/expertise#incident-automation - Manage L2 incidents against SLAs, verify recovery and document the root cause or escalation evidence - Use PowerShell to automate recurring administration and support tasks - Maintain runbooks, troubleshooting procedures, and handover notes that another engineer can follow Systems: Incident Management, Problem Management, SLA Management, Root Cause Analysis, PowerShell, Technical Documentation. ### Delivery and enterprise platform support Working alongside infrastructure and application teams when releases, containers or enterprise applications need support. Source: https://www.prasannasurisetty.com/expertise#delivery-platform-support - Support Azure DevOps deployment and release activity alongside infrastructure and application teams - Assist Docker and AKS environments during platform and application support work - Bring basic Guidewire PolicyCenter familiarity to investigations involving enterprise applications Systems: Azure DevOps, CI/CD, Docker, Kubernetes (AKS), Terraform, Guidewire PolicyCenter fundamentals. ## Support walkthroughs ### Azure Virtual Desktop support Source: https://www.prasannasurisetty.com/experience/enterprise-avd Supporting enterprise virtual desktops from sign-in to session performance, with checks across Entra ID, session hosts, FSLogix and storage. My responsibility: I support host pools, user access and FSLogix profiles, investigate failures using platform logs, and coordinate escalation when another team owns the affected layer. A user sees a failed sign-in, a slow desktop or a temporary profile. The cause may be in identity, desktop assignment, a session host, FSLogix, storage or the network. The first job is to work out which layer is failing before changing anything. Approach: 1. Record the error, affected users, start time and recent changes, then establish whether one user or the wider service is affected 2. Confirm Microsoft Entra ID authentication, access, group membership, user assignment, and application-group scope 3. Check host-pool and session-host availability, active sessions, resource health and platform logs 4. Inspect FSLogix profile attachment, storage reachability, permissions, and profile-container behaviour when the evidence points to the profile layer 5. Compare the logs in Azure Monitor and Log Analytics, verify recovery with the user, and document the checks and fix for handover Recovery checks: - Confirm the original desktop or application opens and the user can complete the task that failed - Check that the intended FSLogix profile loads with the expected data and settings - Complete a normal sign-out, confirm the profile detaches, and record the recovery checks This walkthrough describes my support approach. Client names, tenant details, user records and internal configurations are kept private. ### Azure infrastructure and release support Source: https://www.prasannasurisetty.com/experience/azure-infrastructure-devops Keeping Azure resources and release activity connected, so infrastructure and application teams have the evidence they need when a deployment or service needs attention. My responsibility: I investigate Azure resources alongside release results, support Azure DevOps activity, and assist platform and application owners with Docker and AKS checks. A failed release can look like an application issue while the underlying problem is a virtual machine, storage dependency or network rule. Support needs to connect the deployment result with the state of the infrastructure and bring the right team into the investigation. Approach: 1. Confirm the affected service, deployment scope, timing, change record, user impact, and the last known healthy state 2. Review Azure VM, storage, virtual network, subnet, network security group, and load-balancer state where those resources are in the path 3. Compare the Azure DevOps pipeline or release result with infrastructure logs and application errors 4. Assist with Docker and AKS checks and involve the platform or application owner for changes outside the support team's scope 5. Verify the service after recovery and record the checks, decisions and follow-up work for the next release Recovery checks: - Repeat the check for the affected service and confirm the original symptom has cleared - Review the relevant infrastructure health and deployment results after the approved recovery - Record the verification evidence and any follow-up work for the next release This walkthrough describes my support approach. Client information, environment identifiers, pipeline configurations and network details are kept private. ## Skills Source: https://www.prasannasurisetty.com/about - Azure & Cloud Operations: Microsoft Azure, Azure VMs, Azure Storage, Resource Groups, Azure Monitor, Log Analytics - Azure Virtual Desktop: Azure Virtual Desktop, Host Pools, Session Hosts, Application Groups, FSLogix, User Profile Management - Identity & Access: Microsoft Entra ID, User Provisioning, Group Management, RBAC, Multi-Factor Authentication, Conditional Access, Azure Key Vault - L2 Support & IT Operations: Incident Management, Problem Management, Change Management, SLA Management, Root Cause Analysis, Production Support, Escalation, Remote Support, Technical Documentation - Windows & Endpoint Support: Windows Server 2019/2022, Windows 10/11, User Access, Authentication, System Troubleshooting, Application Troubleshooting - Scripting & Delivery: PowerShell, Azure DevOps, CI/CD, Git, GitHub Actions, Bash, Python (basic) - Networking: TCP/IP, DNS, DHCP, VPN, HTTP/HTTPS, Virtual Networks, Subnets, Network Security Groups, Load Balancer - Platform & Infrastructure Tools: Docker, Kubernetes (AKS), Terraform, ARM Templates, Linux (Ubuntu, CentOS), Guidewire PolicyCenter fundamentals ## Education Bachelor of Engineering, Electronics & Communication Engineering RGM College of Engineering and Technology, 2019 to 2023 Source: https://www.prasannasurisetty.com/about ## Credentials Source: https://www.prasannasurisetty.com/certifications ### Microsoft Certified: Azure Administrator Associate - Issuer: Microsoft - Type: Professional certification - Status: Current - Issued: March 22, 2026 - Expires: March 23, 2027 - Credential ID: 1C30FD93DE16BCF4 - Issuer record: https://learn.microsoft.com/api/credentials/share/en-us/SaiprasannaSurisetty-0424/1C30FD93DE16BCF4?sharingId=96FAB16940BFC920 Azure administration across identity, governance, storage, compute, and virtual networks. ### Microsoft Certified: DevOps Engineer Expert - Issuer: Microsoft - Type: Professional certification - Status: Current - Issued: April 12, 2026 - Expires: April 13, 2027 - Credential ID: 7D9DE9194338856A - Issuer record: https://learn.microsoft.com/api/credentials/share/en-us/SaiprasannaSurisetty-0424/7D9DE9194338856A?sharingId=96FAB16940BFC920 DevOps practices covering delivery pipelines, source control, automation, and reliable releases. ### Fundamentals of Building AI Agents - Issuer: IBM - Type: Course certificate - Status: Current - Issued: February 20, 2026 - Expires: No expiry date listed - Credential ID: T2PLE59FY7FY - Issuer record: https://www.coursera.org/account/accomplishments/records/T2PLE59FY7FY Agent design using tool calling, structured workflows, and LangChain. ### Microsoft 365 Certified: Teams Administrator Associate - Issuer: Microsoft - Type: Professional certification - Status: Past, expired - Issued: May 25, 2025 - Expires: May 26, 2026 - Credential ID: D5AABEA9A931AC59 - Issuer record: https://learn.microsoft.com/api/credentials/share/en-us/SaiprasannaSurisetty-0424/D5AABEA9A931AC59?sharingId=96FAB16940BFC920 Administration of Microsoft Teams collaboration, meetings, calling, and governance. ### Microsoft Certified: Azure Virtual Desktop Specialty - Issuer: Microsoft - Type: Professional certification - Status: Past, expired - Issued: June 6, 2025 - Expires: June 7, 2026 - Credential ID: EE8768F833AD0E43 - Issuer record: https://learn.microsoft.com/api/credentials/share/en-us/SaiprasannaSurisetty-0424/EE8768F833AD0E43?sharingId=96FAB16940BFC920 Planning, deploying, and maintaining Azure Virtual Desktop environments and remote applications. ### Microsoft Certified: Azure Fundamentals - Issuer: Microsoft - Type: Professional certification - Status: Current - Issued: July 9, 2025 - Expires: No expiry date listed - Credential ID: 7645F13F77A9EEB3 - Issuer record: https://learn.microsoft.com/api/credentials/share/en-us/SaiprasannaSurisetty-0424/7645F13F77A9EEB3?sharingId=96FAB16940BFC920 Core cloud concepts, Azure services, security, governance, pricing, and support. ### Microsoft Certified: Azure AI Fundamentals - Issuer: Microsoft - Type: Professional certification - Status: Current - Issued: November 18, 2025 - Expires: No expiry date listed - Credential ID: 283796341874B536 - Issuer record: https://learn.microsoft.com/api/credentials/share/en-us/SaiprasannaSurisetty-0424/283796341874B536?sharingId=96FAB16940BFC920 Foundational machine learning and AI concepts using Microsoft Azure services. ### Microsoft Certified: Azure Data Fundamentals - Issuer: Microsoft - Type: Professional certification - Status: Current - Issued: November 26, 2025 - Expires: No expiry date listed - Credential ID: 7790957F2B192889 - Issuer record: https://learn.microsoft.com/api/credentials/share/en-us/SaiprasannaSurisetty-0424/7790957F2B192889?sharingId=96FAB16940BFC920 Relational and non-relational data concepts, analytics workloads, and Azure data services. ### AI Fluency: Framework & Foundations - Issuer: Anthropic - Type: Course certificate - Status: Current - Issued: December 2025 - Expires: No expiry date listed - Credential ID: jqp4fxx2zeed - Issuer record: https://verify.skilljar.com/c/jqp4fxx2zeed A practical framework for working with AI systems clearly, responsibly, and effectively. ### Google Cloud Certified GenAI Leader - Issuer: Google Cloud - Type: Professional certification - Status: Current - Issued: August 7, 2025 - Expires: August 7, 2028 - Credential ID: 0ad14c8163dd460a9c427e9a46285f80 - Issuer record: https://www.credly.com/badges/189a2bff-c927-477d-808a-b959b4d3e6e6/public_url Generative AI strategy, Google Cloud capabilities, and responsible adoption in organisations. ### Develop Generative AI Applications: Get Started - Issuer: IBM - Type: Course certificate - Status: Current - Issued: November 23, 2025 - Expires: No expiry date listed - Credential ID: XVPDD1D450CY - Issuer record: https://www.coursera.org/account/accomplishments/records/XVPDD1D450CY Building generative AI applications with language models, prompts, and Python tooling. ### Build RAG Applications: Get Started - Issuer: IBM - Type: Course certificate - Status: Current - Issued: December 1, 2025 - Expires: No expiry date listed - Credential ID: 1HK1K5XVSGYQ - Issuer record: https://www.coursera.org/account/accomplishments/records/1HK1K5XVSGYQ Retrieval augmented generation using document retrieval, embeddings, and grounded responses. ## Technical writing --- # Azure Virtual Desktop Sign-In Troubleshooting: An Evidence-First Path By Sai Prasanna Surisetty Published: 2026-08-31 Updated: 2026-08-31 Reviewed: 2026-08-31 Source: https://www.prasannasurisetty.com/blog/azure-virtual-desktop-sign-in-troubleshooting Markdown: https://www.prasannasurisetty.com/blog/azure-virtual-desktop-sign-in-troubleshooting/markdown 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. ## The useful starting point > **Key takeaway** > > I do not treat every Azure Virtual Desktop sign-in failure as an identity problem. I first name the stage that failed, preserve the evidence, and then test the smallest safe hypothesis. The user experience can look almost identical when the actual fault sits in entitlement, the AVD control plane, a session host, network reachability, remote authentication, or the FSLogix profile path. A clear troubleshooting sequence reduces guesswork and makes an escalation useful even when I do not own the failing layer. ## Scope and safety boundary This is a diagnostic framework for support engineers working in an approved Azure Virtual Desktop environment. Tenant architecture, Conditional Access, identity design, host-pool configuration, and change control always take priority over a general checklist. My first pass is read-only. I do not restart a shared session host, change access policy, remove a user assignment, reset an FSLogix container, or clear a session until ownership, impact, rollback, and verification are understood. A quick change can erase the evidence or affect users who are still working. ## Name the failed stage before choosing a fix Microsoft separates authentication into cloud-service, remote-session, and in-session phases. For sign-in triage, I focus on the first two and then follow the journey through session-host processing and profile loading. The exact message, timestamp, client, resource, and last visible screen help identify where the failure began. | Practical stage | What the user may see | First evidence to collect | | --- | --- | --- | | Cloud service authentication | The user cannot authenticate or list assigned resources | Entra sign-in result, account state, assignment, and Conditional Access outcome available to the support role | | Connection and remote authentication | The workspace appears, but the desktop or application does not open | Client details, connection timestamp, error, and session-host selection | | Session-host processing | The connection reaches a host but no usable session starts | Host registration, health checks, capacity, services, and recent changes | | Profile loading | Windows starts but the expected profile does not load | Matching FSLogix log, sessions, storage path, permissions, locks, and capacity | This classification is a hypothesis, not a conclusion. It tells me which evidence to collect next and stops me from applying the same repair to every sign-in complaint. ## Follow the evidence in a deliberate order I begin with scope. Is one user affected, one host, one location, one client type, or the whole host pool? I record the failure time with timezone, the resource selected, the client version, the displayed error, the host if known, and whether the user has another active or disconnected session. - **Identity and entitlement:** confirm the account state, required assignment, group membership, sign-in result, and any Conditional Access outcome available to the support role. - **Host state and health:** check host availability, registration, health checks, drain mode, capacity, recent restarts, and whether the issue follows one host. - **Client and network:** compare the web and desktop clients when permitted, confirm supported versions, and check the required AVD endpoints rather than assuming a general internet test is enough. - **Connection evidence:** correlate the timestamp across Azure Virtual Desktop Insights, activity records, host events, and client diagnostics where those sources are available. - **Profile path:** if the session reaches Windows, review the matching FSLogix profile log, active sessions, storage reachability, effective configuration, permissions, locks, and capacity. I use a separate [FSLogix profile troubleshooting checklist](/blog/fslogix-profile-troubleshooting-checklist) for that branch. > **A useful escalation is a tested hypothesis** > > I record what I observed, what it suggests, the safe checks already completed, what evidence is missing, and which team owns the next decision. I avoid writing a root cause when the evidence only narrows the layer. ## Use the blast radius to choose the next branch - **Many users across many hosts:** check service health, shared identity dependencies, common networking, policy changes, and platform-wide capacity before touching an individual profile. - **Many users on one host:** compare registration, health checks, image, services, resources, and policy with a healthy peer. Drain the host before any approved disruptive action. - **One user across several hosts:** focus on entitlement, identity, sessions, user-specific policy, permissions, and profile state. - **One user on one host:** compare a permitted attempt on a known-good host and inspect the original host's connection and profile evidence. A portal showing **Available** does not prove that the complete user journey works. It is one signal. Likewise, one successful retry does not prove that an intermittent issue is resolved. ## Verify the complete user journey After an approved fix, I repeat the original path with the same resource and a recorded test time. I confirm that the expected desktop or RemoteApp opens, remote authentication completes, the intended profile loads, and the original symptom does not return during a controlled retry. 1. Confirm the expected resource and session host were used. 2. Check that the intended FSLogix profile attached and no temporary profile loaded. 3. Test the application or action that originally failed, not only the desktop shell. 4. Complete a normal sign-out and confirm the session and profile detach cleanly. 5. Record the before-and-after evidence without storing sensitive user or tenant details in public notes. ## Limitations This approach cannot replace tenant-specific architecture, access to the right logs, or the organisation's incident and change procedures. Custom images, security tools, hybrid identity, third-party network controls, and storage designs can create different failure paths. When the evidence is incomplete, I stop at the strongest supported conclusion and make the next escalation specific. Official sources: - Authentication in Azure Virtual Desktop: https://learn.microsoft.com/en-us/azure/virtual-desktop/authentication - Required FQDNs and endpoints for Azure Virtual Desktop: https://learn.microsoft.com/en-us/azure/virtual-desktop/required-fqdn-endpoint - Session host statuses and health checks: https://learn.microsoft.com/en-us/azure/virtual-desktop/session-host-status-health-checks - Azure Virtual Desktop Insights use cases: https://learn.microsoft.com/en-us/azure/virtual-desktop/insights-use-cases - Azure Virtual Desktop troubleshooting documentation: https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-desktop/welcome-virtual-desktop - Troubleshoot long or failed sign-ins with FSLogix: https://learn.microsoft.com/en-us/fslogix/troubleshooting-long-failed-signin --- # FSLogix Profile Troubleshooting: An Azure Virtual Desktop Checklist By Sai Prasanna Surisetty Published: 2026-08-22 Updated: 2026-08-31 Reviewed: 2026-08-31 Source: https://www.prasannasurisetty.com/blog/fslogix-profile-troubleshooting-checklist Markdown: https://www.prasannasurisetty.com/blog/fslogix-profile-troubleshooting-checklist/markdown 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. ## Start with the evidence, not the container > **Key takeaway** > > I do not begin by deleting a local profile, renaming a VHDX, or restarting services. I first identify the blast radius, preserve the matching sign-in evidence, and follow the failure to the layer that owns it. The same user report can describe a temporary profile, an attach failure, an unavailable SMB path, a stale session lock, insufficient capacity, or an application-only issue. A repeatable checklist protects user data and keeps the diagnosis focused. If the failure occurs before Windows begins loading the profile, I return to the broader [Azure Virtual Desktop sign-in troubleshooting path](/blog/azure-virtual-desktop-sign-in-troubleshooting) instead of forcing the symptom into an FSLogix branch. ## Scope and safety boundary This checklist is for support engineers investigating FSLogix Profile Containers in Azure Virtual Desktop. It assumes the storage design, identity model, permissions, backup, and change procedures are already approved for the environment. The initial checks are read-only. I never force-detach a container, remove a lock, change permissions, delete a profile, or mount a user's VHDX while a session may still be active. Those actions require confirmed ownership, a recovery path, an approved window, and a clear verification plan. ## Classify the symptom before troubleshooting 1. **Temporary, local, or default profile:** settings and files appear missing. 2. **Slow or failed sign-in:** the user waits, sees an FSLogix message, or never reaches the desktop. 3. **Attach or detach failure:** the logs record a VHD or VHDX operation error. 4. **Container locked or in use:** another session is active or did not close cleanly. 5. **Capacity or performance issue:** the container, backing share, or session host is constrained. 6. **Application-only symptom:** Windows loads the expected profile, but one application or redirection fails. This classification does not prove the cause. It prevents a broad reset-the-profile response when the evidence points elsewhere. ## Build the evidence set before changing anything I record the failure time, affected user, host, session ID and state, FSLogix version, and displayed message. The timestamp and host separate the event from overlapping or disconnected sessions. - The matching Profile log under `C:\ProgramData\FSLogix\Logs\Profile`, following the relevant `LoadProfile` sequence and process ID. - FSLogix Apps Admin and Operational events, plus Cloud Cache logs when Cloud Cache is part of the design. - The FSLogix version, service state, and effective policy compared with a known-good host. - The effective `VHDLocations` or `CCDLocations` value, verified through policy results and logs rather than one isolated registry value. - Name resolution and SMB reachability from the affected host. - The user's complete permission path. Administrator access does not prove that the user has the required share, NTFS, or Azure RBAC permissions. - Free capacity, latency, availability, and health of the backing share and profile container. - Active and disconnected sessions across the pool, because a live session can legitimately hold an exclusive lock. ```powershell Test-NetConnection -ComputerName -CommonTCPPort SMB ``` I treat **Access is denied**, **Path not found**, and **File in use** as different branches. The wording is evidence, not a reason to try the same repair three times. ## Let the blast radius choose the next branch | Scope | Most useful next branch | | --- | --- | | Many users across many hosts | Shared storage, DNS, SMB connectivity, authentication, permissions or RBAC, platform health, and recent changes | | Many users on one host | Version, policy, services, image, filter drivers, resources, and storage reachability compared with a healthy peer | | One user across multiple hosts | Sessions and locks, permissions, profile folder and SID mapping, capacity, and local or temporary profile state | | One user on one host | A permitted comparison on a known-good host, followed by evidence from the original host and storage path | > **Read the error in context** > > Access denied suggests identity or permissions. Path not found suggests configuration, DNS, routing, or SMB access. Container locked requires confirmed session ownership. Low space requires checking both the VHDX and its backing share. Suspected corruption comes only after those causes are excluded. ## Verify recovery, not only sign-in A visible desktop is only the first check. I confirm that FSLogix attached the intended container, no temporary or local profile loaded, and the log shows a clean attach sequence. - Confirm the user's expected data and settings are present. - Test the applications involved in the original report. - Complete a normal sign-out and confirm the container detaches cleanly. - Use a controlled second sign-in when the change process allows it. - Document the host, timestamp, version, evidence, cause, action, and verification without exposing user or tenant details. ## Prevention I would build into operations - Monitor storage capacity, latency, availability, and authentication failures before users report missing profiles. - Keep profile storage close to the session hosts and size it for the measured workload. - Standardise FSLogix versions, image configuration, policy, share permissions, NTFS ACLs, and Azure RBAC across the pool. - Test updates and configuration changes on a limited host set before a broad rollout. - Review cleanup, temporary-profile, and login-prevention settings as design decisions because each changes user experience or data handling. - Restrict access to profile containers and use the storage provider's current network and security controls. - Check the current FSLogix known issues and release notes before creating a workaround for a version-specific fault. ## Limitations and review date This is a triage framework, not a universal repair procedure. Standard containers, Cloud Cache, Azure Files, Azure NetApp Files, Active Directory, Microsoft Entra joined hosts, hybrid identities, security products, and application redirections can produce different evidence. Product guidance and known issues change. I reviewed the linked sources on 31 August 2026 and would recheck them before using this checklist later. Official sources: - Troubleshooting with FSLogix logs and diagnostics: https://learn.microsoft.com/en-us/fslogix/troubleshooting-events-logs-diagnostics - Troubleshoot old, temporary, or local profiles: https://learn.microsoft.com/en-us/fslogix/troubleshooting-old-temp-local-profiles - Troubleshoot long or failed sign-ins: https://learn.microsoft.com/en-us/fslogix/troubleshooting-long-failed-signin - Troubleshoot container lock or in-use issues: https://learn.microsoft.com/en-us/fslogix/troubleshooting-container-locked - Troubleshoot container size or low disk space: https://learn.microsoft.com/en-us/fslogix/troubleshooting-container-size-space - FSLogix known issues: https://learn.microsoft.com/en-us/fslogix/troubleshooting-known-issues - FSLogix Profile Container storage for Azure Virtual Desktop: https://learn.microsoft.com/en-us/azure/virtual-desktop/store-fslogix-profile - FSLogix container storage options: https://learn.microsoft.com/en-us/fslogix/concepts-container-storage-options