Field note / 15 December 2010
Keeping the SharePoint web application count under control
Every web application adds a boundary, a pool and a set of dependencies. Some boundaries are worth it. Many are not.
A web application is a large administrative boundary in SharePoint. It brings an IIS site, an application pool, a database, authentication settings and often a separate URL. Creating one is easy enough that teams can accumulate them without noticing the operational weight.
Each addition increases patching, monitoring, certificate and service account work. It also fragments the service application configuration and makes it harder to explain which URL belongs to which business capability.
Ask whether a site collection would do
If two workloads can share authentication, URL structure and service configuration, a site collection may provide enough separation. A new web application is justified when the security boundary, the host name or the application pool really needs to be independent.
Review the existing web applications before adding another. Record the owner, purpose, URL, authentication model and dependent service applications. A short register makes duplication visible and gives a future architect a chance to consolidate rather than inherit a maze.
The short list
Checks worth running
- Confirm that the new requirement cannot be met with a site collection.
- Record the owner and purpose of every web application.
- Review the count and the shared dependencies during design reviews.
Consolidation is easier before a boundary exists. The question is not whether another web application can be created. It is whether the organisation can support the additional surface it creates.
Outside reading
Reference shelf
Official documentation and independent community reading for the subjects in this note.
- Microsoft Learn: SharePoint administration (opens in a new tab)Operational guidance for service settings, site management and the modern admin experience.
- Microsoft Learn: SharePoint documentation (opens in a new tab)The starting point for current SharePoint administration, development and hybrid guidance.
- Microsoft Support (opens in a new tab)Support articles, troubleshooting steps and product help from Microsoft.
- Microsoft Learn: SQL Server documentation (opens in a new tab)Official reference material for database engine configuration, performance and recovery.
- Microsoft Learn: IIS documentation (opens in a new tab)Reference material for web server configuration, authentication and diagnostics.
- Microsoft Tech Community (opens in a new tab)Community discussion, product announcements and practical posts from Microsoft teams.
- Microsoft Learn Q&A (opens in a new tab)A community question and answer space hosted by Microsoft.
- SharePoint Stack Exchange (opens in a new tab)An independent question and answer community for SharePoint practitioners.
- Microsoft Download Center (opens in a new tab)Official downloads for Microsoft tools, updates and supporting packages.
- Microsoft Learn: Windows Server documentation (opens in a new tab)Current guidance for Windows Server roles, networking, storage and management.
- Microsoft Security Response Center (opens in a new tab)Security advisories, update guidance and vulnerability response information.
- SharePoint community on Reddit (opens in a new tab)An independent discussion space for administrators, developers and users.
- Microsoft Learn: Azure Architecture Center (opens in a new tab)Reference architectures and design guidance for resilient cloud workloads.
- Microsoft Learn: SharePoint search (opens in a new tab)Documentation for search architecture, crawling and result management.
- Microsoft Learn: PowerShell documentation (opens in a new tab)Language reference, cmdlet documentation and guidance for repeatable automation.