Summary
Details
Updated October 20, 2025: Removal of these pages have started in late October 2025 and will be fully completed by end of November 2025.
ASP.NET DISCO and WSDL pages were the web service APIs for customers who wanted to create a proxy for their web services. The retirement of ASP.NET web services was announced in 2013 and should not be used. We encourage customers to move away from consuming these pages and use Microsoft Graph for remote operations where possible.
Please refer to the following information regarding the DISCO and WSDL endpoints
- These endpoints were originally designed for use with development tools from the early 2000s and were never a preferred or widely adopted method for generating proxy classes in SharePoint development.
- These endpoints are not tenant-specific and are not associated with any individual tenant’s configuration or ownership.
- Usage across the SharePoint Online service is extremely rare. In fact, most of these endpoints show zero usage.
- These endpoints were primarily used in legacy development scenarios and are not required for modern SharePoint development practices.
- If your organization has an internal development team, we recommend consulting with them to confirm whether these endpoints are in use. However, it is extremely unlikely that they are being used in any current development workflows.
Learn more: Removal of deprecated DISCO & WSDL aspx pages from SharePoint Online - Microsoft 365 Developer Blog
Change History
Updated September 4, 2025: After further review, the original deprecation decision and goal remain unchanged. At this time, we are deferring the effective date. We will communicate the timeline when we are ready to proceed and remove these web pages. We apologize for any inconvenience.
ASP.NET DISCO and WSDL pages were the web service APIs for customers who wanted to create a proxy for their web services. The retirement of ASP.NET web services was announced in 2013 and should not be used. We encourage customers to move away from consuming these pages and use Microsoft Graph for remote operations where possible.
Please refer to the following information regarding the DISCO and WSDL endpoints
- These endpoints were originally designed for use with development tools from the early 2000s and were never a preferred or widely adopted method for generating proxy classes in SharePoint development.
- These endpoints are not tenant-specific and are not associated with any individual tenant’s configuration or ownership.
- Usage across the SharePoint Online service is extremely rare. In fact, most of these endpoints show zero usage.
- These endpoints were primarily used in legacy development scenarios and are not required for modern SharePoint development practices.
- If your organization has an internal development team, we recommend consulting with them to confirm whether these endpoints are in use. However, it is extremely unlikely that they are being used in any current development workflows.
Learn more: Removal of deprecated DISCO & WSDL aspx pages from SharePoint Online - Microsoft 365 Developer Blog
Updated October 20, 2025: Removal of these pages have started in late October 2025 and will be fully completed by end of November 2025.
ASP.NET DISCO and WSDL pages were the web service APIs for customers who wanted to create a proxy for their web services. The retirement of ASP.NET web services was announced in 2013 and should not be used. We encourage customers to move away from consuming these pages and use Microsoft Graph for remote operations where possible.
Please refer to the following information regarding the DISCO and WSDL endpoints
- These endpoints were originally designed for use with development tools from the early 2000s and were never a preferred or widely adopted method for generating proxy classes in SharePoint development.
- These endpoints are not tenant-specific and are not associated with any individual tenant’s configuration or ownership.
- Usage across the SharePoint Online service is extremely rare. In fact, most of these endpoints show zero usage.
- These endpoints were primarily used in legacy development scenarios and are not required for modern SharePoint development practices.
- If your organization has an internal development team, we recommend consulting with them to confirm whether these endpoints are in use. However, it is extremely unlikely that they are being used in any current development workflows.
Learn more: Removal of deprecated DISCO & WSDL aspx pages from SharePoint Online - Microsoft 365 Developer Blog
Updated May 22, 2025: We have updated the content. Thank you for your patience.
ASP.NET DISCO and WSDL pages were the web service APIs for customers who wanted to create a proxy for their web services. The retirement of ASP.NET web services was announced in 2013 and should not be used. We recommend using Microsoft Graph for remote operations where possible.
We will remove these pages from Microsoft SharePoint Online starting mid-August 2025 and ending in mid-September 2025.
Please refer to the following information regarding the DISCO and WSDL endpoints
- These endpoints were originally designed for use with development tools from the early 2000s and were never a preferred or widely adopted method for generating proxy classes in SharePoint development.
- These endpoints are not tenant-specific and are not associated with any individual tenant’s configuration or ownership.
- Usage across the SharePoint Online service is extremely rare. In fact, most of these endpoints show zero usage.
- These endpoints were primarily used in legacy development scenarios and are not required for modern SharePoint development practices.
- If your organization has an internal development team, we recommend consulting with them to confirm whether these endpoints are in use. However, it is extremely unlikely that they are being used in any current development workflows.
Learn more: Removal of deprecated DISCO & WSDL aspx pages from SharePoint Online - Microsoft 365 Developer Blog
Updated September 4, 2025: After further review, the original deprecation decision and goal remain unchanged. At this time, we are deferring the effective date. We will communicate the timeline when we are ready to proceed and remove these web pages. We apologize for any inconvenience.
ASP.NET DISCO and WSDL pages were the web service APIs for customers who wanted to create a proxy for their web services. The retirement of ASP.NET web services was announced in 2013 and should not be used. We encourage customers to move away from consuming these pages and use Microsoft Graph for remote operations where possible.
Please refer to the following information regarding the DISCO and WSDL endpoints
- These endpoints were originally designed for use with development tools from the early 2000s and were never a preferred or widely adopted method for generating proxy classes in SharePoint development.
- These endpoints are not tenant-specific and are not associated with any individual tenant’s configuration or ownership.
- Usage across the SharePoint Online service is extremely rare. In fact, most of these endpoints show zero usage.
- These endpoints were primarily used in legacy development scenarios and are not required for modern SharePoint development practices.
- If your organization has an internal development team, we recommend consulting with them to confirm whether these endpoints are in use. However, it is extremely unlikely that they are being used in any current development workflows.
Learn more: Removal of deprecated DISCO & WSDL aspx pages from SharePoint Online - Microsoft 365 Developer Blog
Never Miss a Microsoft 365 Update
Join thousands of IT professionals who rely on DeltaPulse for real-time Microsoft 365 change intelligence, automated notifications, and community insights.