Microsoft sharepoint server details

Question

Hi.

I have one doubt: if one user had taken ISP service broadband or ILL and that user downloaded one file from SharePoint that is publicly hosted, like [Moderator note: personal info removed], in total how many users are transmitting data in this server and how much bandwidth link is given? How to know all of this?

One more server-side restriction, like pipelines for users, such as bandwidth (example: a 100 Gbps link given (server) to 10000 people downloading the files with this server on weekends, each person having some bandwidth (10 Mbps)), after users go from 10001 users to 20000 users, speed will reduce. How to know a user is restricted from this server?

This kind of issue arises in client locations. If users found only one problem, an internet issue, they will not check other sites and others.

Answer 1

Please note that Q&A forum is a public platform, and moderators will modify the question to hide personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.

Hi @Subbu

Based on the scenario you described, I understand you are trying to figure out how SharePoint manages bandwidth allocation, data transmission volumes, and server-side constraints (like throttling) when a large number of users are downloading publicly hosted files simultaneously over an ISP connection. You also want to know how to detect if a client is being restricted by the server rather than their own internet connection.

Here is a technical breakdown of how SharePoint handles this under the hood, written in clear English for your reference or to share with your clients:

1. How SharePoint Allocates Bandwidth

SharePoint Online does not rely on a single server with a fixed rigid pipeline (like a standalone 100 Gbps link) that gets evenly sliced among concurrent users.

• Global CDN and Edge Locations: SharePoint relies heavily on a global Content Delivery Network (CDN) with thousands of distributed edge points worldwide. When a user downloads a publicly hosted file, the file is usually cached and served from the edge location geographically closest to that user. This distributed system dramatically reduces the load on the origin server and scales dynamically based on regional demand.
• No Fixed Mbps Per User: There are no official public Microsoft documents specifying an exact, fixed bandwidth cap (like "10 Mbps per user"). Microsoft does not allocate bandwidth on a strict per-megabit basis; instead, the system dynamically manages data flow based on overall infrastructure health and real-time demand.

2. Server-Side Restrictions: Understanding Throttling

Since SharePoint is a multi-tenant cloud environment, Microsoft implements throttling to protect the integrity and stability of the service.

• If thousands of users suddenly flood the system to download massive files simultaneously (such as during a weekend peak), throttling kicks in. This prevents a specific group of users or a single tenant from monopolizing all the shared cloud resources and causing a platform-wide outage.
• When throttling occurs, SharePoint will deliberately restrict user speeds by reducing throughput, or it will temporarily block requests entirely by returning an HTTP 429 (Too Many Requests) error code.

3. How to Know if a User is Restricted by the Server

• While Microsoft does not provide a direct real-time dashboard showing exactly how many users are actively downloading from a specific server or the exact bandwidth link size, you can diagnose a server-side restriction by analyzing throttling behavior:
• If you monitor the network traffic (via Browser Developer Tools F12 > Network tab) during a slow download, look at the server response. If the server is actively rejecting or delaying the request due to high load, it will throw an HTTP 429 or 503 error instead of a standard HTTP 200 success code.

For a deeper dive into how Microsoft governs these limits and how to optimize your environment to prevent it, you can review this official technical article:

Avoid getting throttled or blocked in SharePoint Online

https://github.com/MicrosoftDocs/microsoft-365-docs/blob/public/microsoft-365/enterprise/content-delivery-networks.md

I hope this information help!

---

If the answer is helpful, 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 related email notification for this thread.

Answer 2

For a publicly reachable SharePoint (or SharePoint Online) endpoint such as 13.107.136.10, there is no way from the client side to see:

• How many total users are currently downloading from that server
• What total bandwidth is provisioned to that server
• How bandwidth is shared among all users globally

Those details are internal to the service provider (Microsoft or the hosting organization) and are not exposed to end users.

What can be observed from the client side is only:

• The effective download throughput for that client (for example, MB/s when downloading a file)
• Latency, packet loss, and similar network metrics between the client and the service

For Microsoft 365, Microsoft measures some of these metrics to assess network quality. For SharePoint/OneDrive, the download speed is measured in megabytes per second, and a 25th percentile (P25) over three days is used to score performance. For Microsoft Teams, UDP latency, jitter, and packet loss are measured and converted into a quality score. These assessments are about user experience, not about exposing internal capacity or per-user throttling details.

Regarding server-side restrictions and per-user bandwidth:

• SharePoint Server and SharePoint Online can be affected by WAN bandwidth, latency, and congestion. Microsoft has optimized SharePoint Server 2013 and Microsoft 365 to use available bandwidth more efficiently (for example, better TCP/IP utilization, compression, minimal download strategy), but this does not expose per-user bandwidth allocations.
• If many users share a limited WAN or internet link (for example, 100 Gbps shared by many thousands of users), each user’s effective speed will drop as contention increases. This is a property of the network path and local ISP/enterprise WAN, not something that can be directly read from the SharePoint endpoint.
• SharePoint has various limits and thresholds (for example, response latency thresholds, service response size limits, content database limits), but these are about request size, timeouts, and capacity planning, not about publishing per-user bandwidth caps to clients.

How to detect if a user is being limited or impacted:

1. Measure client-side throughput and latency
   • Download a representative file from SharePoint and record the MB/s throughput.
   • Repeat at different times (peak vs off-peak) to see if performance degrades when more users are active.
2. Compare with expected WAN/ISP capacity
   • If the user’s measured throughput is consistently far below what the local circuit should support, this suggests congestion or throttling somewhere on the path (ISP, corporate WAN, or intermediate devices).
3. Use Microsoft 365 network assessment data (if available)
   • In Microsoft 365 network assessments, the SharePoint download speed P25 metric and Teams network quality scores can indicate whether users at a given location are experiencing poor performance due to network issues.
4. Check internal network and capacity planning
   • On-premises SharePoint Server deployments rely on proper capacity planning (workload, concurrent users, content size, latency/throughput targets). If many users share limited WAN links, the organization must size and monitor those links; SharePoint itself does not expose a “this user is throttled” flag to the client.

In summary, there is no client-visible indicator that says “this user is restricted to X Mbps by the SharePoint server.” Performance issues at client locations must be diagnosed by measuring network performance (throughput, latency) and comparing against expected WAN/ISP capacity, combined with internal monitoring and capacity planning.

---

References:

• Microsoft 365 network assessment
• Testing WAN connections for SharePoint 2013 architectures
• Capacity planning for SharePoint Server 2013
• Software boundaries and limits for SharePoint 2013
• Estimate capacity and performance for Web Content Management (SharePoint Server 2013)
• SharePoint limits