Inquiry about the Deprecation of WebClient/WebDAV Services, Overall Impact, and Replacement Options

This is a question hard to get an answer from a forum. If you can go through Microsoft support via a support ticket and share more of your scenarios, you might be able to get better insight.

My personal understanding of your reference is,

1. In short, WebDAV is a very old protocol aiming to enable typical scenarios such as file sharing. But during the past decades none of the popular applications in this field (Dropbox, OneDrive and others) have chosen this direction. Thus, if the Windows client OS one day stops supporting WebDAV like the announcement says, people shouldn't be surprised because the majority (if not all) of them are using a non-WebDAV solution.
2. I don't think this specific announcement you referred to covers WebDAV on the server side (aka IIS). (Similarly the previous announcement to deprecate VBScript on the Windows client wasn't extended to classic ASP on IIS.) But if you are still using WebDAV on IIS, try to switch to a modern alternative.
3. The announcement talks about "Webclient (WebDAV) Service" which is a Windows 10/11 component that connects to a WebDAV server. So don't get confused with WebClient in .NET programming, which is irrelevant and a different thing.
4. There are quite a few options to migrate to, and I believe OneDrive/SharePoint from Microsoft covers many of the key features you might need.

Hi @Ramkumar M,

The Webclient WebDAV service, once a prominent feature in Windows, has been officially deprecated. This indicates that Microsoft is gradually reducing the help and updates for this service, showing that they plan to stop using it in upcoming versions of the operating system.

Currently, the Webclient service is no longer started by default in Windows. Users who rely on WebDAV functionality will need to manually enable the service if they wish to continue using it. Microsoft didn't give an exact reason for its deprecation, but it is to be imagined that they are along the same lines as the previous ones.

When such deprecations occur, they are usually deliberate. It could be due to security concerns, outdated technology, or a shift in focus to newer, more efficient protocols. Although Microsoft offices did not issue a statement about this, nor mentioned it on social networks or anywhere else, outdated technology will eventually disappear.

This shift highlights the importance of exploring alternative solutions for WebDAV-related tasks, as it may no longer be a viable long-term option for specific applications or workflows within the Windows environment.

WebDAV isn’t the only Internet protocol that lets you work with files on a remote server. There are several alternatives, including cloud storages, and each offers unique advantages and features that serve different purposes.

Since the Windows WebDAV client will remain in Windows for the foreseeable future, you can plan the migration accordingly. Please first evaluate the impact on your application and identify all locations where WebClient or WebDAV functionality is used. Develop a migration plan that includes updating code, thorough testing, and providing proper documentation to developers. If feasible, consider a gradual migration strategy to minimize disruption to application functionality.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the email notification for this thread.

Best regards,

Yurong Dai