# Check File Sync progress inside a failed session

> Use applied-item evidence and persistent per-item errors to distinguish partial progress from a stalled sync.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-181-check-file-sync-progress-inside-a-failed-session/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:28:55+00:00
- Modified: 2026-09-10T00:55:36+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Cybersecurity, Networks & Infrastructure
- Reading time: 1 minutes

## What you need to know

Use applied-item evidence and persistent per-item errors to distinguish partial progress from a stalled sync.

## Potentially affected

Azure File Sync server endpoints reporting failed sessions or per-item errors.

## DSE recommendation

Review applied counts and persistent item failures before treating the entire session as making no progress.

## Article

## Source facts

A File Sync session can fail overall or report per-item errors while still synchronizing some files. Microsoft identifies the Applied fields as evidence of how much succeeded, rather than treating the aggregate result as a complete description.

Event 9121 is recorded for each per-item error after the session finishes and provides persistent and transient counts. Microsoft specifically advises investigating persistent per-item errors. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-monitoring).

## Applicability

Identify the affected server endpoint, session interval, and files whose availability matters. Keep overall session status, observed progress, and unresolved item failures separate in the incident record.

## DSE recommendation

DSE recommends comparing consecutive session evidence before choosing the next action. Record which applied counts are changing and which item errors persist. Ask the file-service owner to prioritize unresolved business-critical files rather than dismissing the incident because other files made progress. Avoid restarting or rebuilding the endpoint solely from the aggregate failure label.

## Verification

For an approved sample, reconcile applied-file evidence with the destination and inspect the corresponding per-item events. Confirm whether the next session advances and whether the same items remain blocked. Preserve endpoint identity, session timestamps, relevant counters, and sanitized error details so another operator can reproduce the diagnosis.

## Official references

[Microsoft Learn: Monitor Azure File Sync](https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-monitoring). Source retrieved September 9, 2026.

## Primary reference

- Name: Monitor Azure File Sync | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-monitoring
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Check File Sync progress inside a failed session,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-181-check-file-sync-progress-inside-a-failed-session/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.