# SharePoint site

> Source: Courseiva IT Certification Glossary — https://courseiva.com/glossary/sharepoint-site

## Quick definition

A SharePoint site is like a team’s own private website where everyone can store files, share updates, and work together. You can set it up for a project, a department, or the whole company. It helps people find information and collaborate easily without emailing files back and forth.

## Simple meaning

Think of a SharePoint site as a digital clubhouse for your team. Just like a physical clubhouse has rooms for different activities, a SharePoint site gives you a central place where your team can store shared documents, post announcements, manage tasks, and keep track of important information. Instead of sending files as email attachments that get lost or become outdated, everyone goes to the same SharePoint site to find the latest version.

For example, imagine your family shares a house. In that house, there is a kitchen where everyone can find the grocery list, a living room where you hang family photos, and a bulletin board in the hallway for reminders. A SharePoint site works the same way. It has libraries for documents, lists for tracking tasks, pages for news, and calendars for events. Each team member can access the site from a web browser or a mobile app, and they only see what they have permission to see.

SharePoint sites are built on SharePoint, which is part of Microsoft 365 (formerly Office 365). When your company subscribes to Microsoft 365, it gets a SharePoint environment where you can create as many sites as you need. Each site comes with default apps like a document library, a site pages library, and a newsfeed. You can also add custom apps, like a task list or a calendar. In short, a SharePoint site is a central hub that helps teams stay organized, communicate better, and work together on shared content.

## Technical definition

A SharePoint site is a container within Microsoft SharePoint that aggregates web parts, lists, libraries, pages, permissions, and features to provide a focused collaboration environment. Each SharePoint site is hosted on a SharePoint farm or in SharePoint Online (part of Microsoft 365). The site is defined by a unique URL (e.g., https://contoso.sharepoint.com/sites/ProjectX) and is backed by a content database that stores all its data.

Architecturally, a SharePoint site is built on a site collection. A site collection is a hierarchical set of sites that share common features, navigation, permissions, and administration settings. The top-level site in the collection is called the root site, and child sites can be created under it. Each site collection has its own content database, which improves scalability and manageability.

The core components of a SharePoint site include:
- Lists: Structured data storage, such as custom lists, calendars, issue trackers, and contacts. Lists support columns, views, and validation rules.
- Libraries: Specialized lists optimized for storing documents, images, and other files. Document libraries support versioning, check-out/check-in, content approval, and metadata.
- Web Parts: Modular components that display content on site pages. Examples include the Document Library web part, the Calendar web part, and the News web part.
- Pages: ASP.NET-based pages that can contain web parts, text, images, and rich content. Pages can be wiki pages, web part pages, or publishing pages (in Publishing sites).
- Permissions: Security is managed through SharePoint groups and permission levels. Site owners can assign unique permissions to sites, lists, folders, or items.
- Features: SharePoint features activate or deactivate functionality at the site or site collection level. Examples include the Team Collaboration Lists feature, the Publishing feature, and the Enterprise Search feature.

In terms of protocols, SharePoint communicates primarily over HTTPS (HTTP over TLS). When accessing a SharePoint site, the client (browser or Office app) sends requests to the SharePoint server using REST APIs or the older SOAP-based web services. SharePoint Online uses Azure Active Directory for authentication and authorization. In on-premises deployments, authentication can be Windows Integrated (NTLM or Kerberos), forms-based, or claims-based.

From an IT implementation perspective, deploying a SharePoint site involves provisioning a site collection, choosing a site template (Team site, Communication site, Publishing site, etc.), configuring storage quotas, setting up permissions, and enabling necessary features. Administrators can use SharePoint Central Administration (on-premises) or the SharePoint Admin Center (Online) to manage sites. Site owners can further customize the site using the browser interface, SharePoint Designer, or PowerShell scripts.

Real-world IT professionals must also consider governance, compliance, and retention policies. SharePoint sites can be subject to information management policies, data loss prevention (DLP) rules, and eDiscovery holds. Backup and disaster recovery strategies must account for site content, and monitoring tools like SharePoint Health Analyzer (on-premises) or the Microsoft 365 admin center help ensure site availability and performance.

## Real-life example

Imagine you are part of a volunteer group organizing a community festival. Your group has several committees: the food committee, the entertainment committee, the logistics committee, and the marketing committee. In the past, everyone used email to share ideas, people attached outdated spreadsheets, conversations got scattered across inboxes, and nobody could find the final version of the vendor list. It was chaotic.

Now, you decide to create a SharePoint site for your festival team. Think of the SharePoint site as the new online clubhouse for all volunteers. The site has a homepage that shows a welcome message and the latest announcements. It has a document library where the food committee stores the approved menu, the logistics committee uploads the layout map, and the marketing committee saves the press release drafts. Instead of emailing files, everyone goes to the same library, takes the latest version, and checks it out so nobody else edits at the same time. When someone makes a change, the site saves a new version automatically, so you can always go back to an older version if someone accidentally deletes the vendor list.

The site also includes a shared calendar where all committees add their meeting dates and deadlines. There is a task list that tracks who is responsible for each action item. For example, the marketing committee has a task to "Design flyer by May 15" with a status of "In Progress." If the logistics committee has a question about the venue, they can post a message on the site's discussion board, and the entire team sees the answer.

Because the site is online, volunteers can access it from home, on their phones, or at the library. The festival coordinator sets permissions so that only committee leads can edit certain folders, while all volunteers can view everything. This ensures sensitive information, like volunteer contact details, stays private. In the end, the festival runs smoothly because everyone has one single source of truth, the SharePoint site.

## Why it matters

SharePoint sites matter because they provide a centralized, secure, and scalable platform for team collaboration in modern organizations. In an IT context, understanding SharePoint sites is essential for administrators, help desk staff, and developers who need to deploy, configure, troubleshoot, or customize collaboration solutions. Without a clear grasp of how SharePoint sites work, IT professionals cannot effectively manage permissions, storage, or performance, leading to security risks, data loss, and user frustration.

From a business perspective, SharePoint sites eliminate the chaos of email-based collaboration. When employees use SharePoint instead of email attachments, version control becomes automatic, access can be controlled granularly, and information is discoverable through search. This reduces the time spent looking for files and prevents costly errors from using outdated documents. IT teams can also enforce compliance by applying retention labels, eDiscovery holds, and DLP policies on site content.

For IT professionals, managing SharePoint sites is a core responsibility. In SharePoint Online, administrators use the SharePoint Admin Center to create site collections, set storage limits, manage external sharing, and monitor activity. In on-premises deployments, they must also manage content databases, service applications, and web applications. Understanding site hierarchy, site collections, sites, subsites, and workspaces, is crucial for proper capacity planning and backup strategies.

SharePoint sites integrate with other Microsoft 365 services like Microsoft Teams, Power Platform, and OneDrive. For example, every Microsoft Team gets a linked SharePoint site behind the scenes for file storage. When an IT professional understands SharePoint sites, they can troubleshoot file sync issues, optimize search results, and configure hybrid scenarios where on-premises sites connect to cloud-based resources.

Finally, SharePoint sites are frequently tested on IT certification exams such as Microsoft 365 Certified: Fundamentals (MS-900), Microsoft 365 Certified: Administrator Expert (MS-102), and Microsoft Certified: SharePoint Administrator Associate. These exams require you to know how to provision, configure, secure, and monitor SharePoint sites. Mastery of this concept is a stepping stone to advanced roles in cloud administration and enterprise content management.

## Why it matters in exams

SharePoint sites are a recurring topic across multiple Microsoft certification exams, especially those focusing on Microsoft 365 administration and collaboration. For the Microsoft 365 Certified: Fundamentals (MS-900) exam, you need to understand what SharePoint sites are at a conceptual level, how they fit into the Microsoft 365 ecosystem, and their primary use cases, such as team collaboration, document management, and intranet portals. Questions may ask you to identify when to use a SharePoint site versus a Microsoft Team or OneDrive. They will also test your knowledge of the different site templates (Team site vs. Communication site) and their typical applications.

On the Microsoft 365 Certified: Administrator Expert (MS-102) exam, the focus shifts to administration and governance. Expect scenario-based questions where you must decide how to configure site permissions, manage external sharing, set storage quotas, or enforce compliance policies. You may also encounter questions about site collection administration, site collection backups, and how to restore deleted sites. Performance-based labs require you to walk through the SharePoint Admin Center to create a new site collection, assign administrators, and apply a retention policy.

The Microsoft Certified: SharePoint Administrator Associate (SPAdmin) exam dives deep into SharePoint-specific administration. Here, you must know the architecture of site collections and subsites, how to manage content databases, and how to configure service applications like Managed Metadata or Search. Questions often test your understanding of features like in-place holds, site policies, and site collection health checks. You will also need to know PowerShell cmdlets for automating SharePoint site management, such as New-SPSite, Set-SPSiteAdministration, and Get-SPSite.

For the Microsoft 365 Certified: Teams Administrator Associate (MS-700) exam, understanding SharePoint sites is indirectly important because every Microsoft Team is backed by a SharePoint team site. Questions may ask you about file sharing, permission inheritance, or how to configure the linked SharePoint site for a team. Troubleshooting questions may involve resolving issues with file access or sync failures that originate from the underlying SharePoint site configuration.

Other exams, such as Microsoft Certified: Power Platform Fundamentals (PL-900) or Microsoft Certified: Power Platform App Maker Associate (PL-100), touch on SharePoint sites as a data source for apps and flows. You might be asked how to create a canvas app from a SharePoint list or how to trigger a Power Automate flow when a new item is added to a SharePoint list.

In all these exams, the question types range from multiple-choice (choose the correct site template for a given scenario) to drag-and-drop (sequence steps to configure external sharing) to case studies (analyze a company’s collaboration requirements and recommend a site architecture). Mastering SharePoint sites, their templates, permissions, storage limits, integration with other services, and administration tools, is essential for passing these certifications with confidence.

## How it appears in exam questions

Exam questions about SharePoint sites typically fall into several patterns: scenario-based design, configuration steps, permission management, troubleshooting, and integration.

Scenario-based questions present a fictional organization with specific collaboration needs. For example: "Contoso Ltd. has a marketing team that wants a central place to share announcements and store campaign documents. They do not need chat or meetings. Which SharePoint site template should be used?" The correct answer would be a Communication site because it is designed for broadcasting information to a broad audience, whereas a Team site is better for collaboration with group chat and Planner integration. Another scenario might ask: "The HR department needs a site where only HR managers can edit documents, but all employees can view them. How should permissions be configured?" The answer involves breaking permission inheritance on the document library and assigning unique permissions.

Configuration questions test your knowledge of the administration interface. For instance: "You need to prevent users from sharing SharePoint site content with people outside the organization. What setting should you configure in the SharePoint Admin Center?" The correct answer is to modify the external sharing settings at the organization level or site collection level, setting it to "Only people in your organization." Another example: "How do you set a storage quota for a new site collection?" You would answer that you specify the maximum storage during site collection creation in the SharePoint Admin Center or via PowerShell.

Permission management questions appear frequently. A typical question: "A user reports that they cannot delete a document from a SharePoint site library, even though they are a member of the site. What is the most likely reason?" The answer could be that the library has unique permissions that grant only "Contribute" without the "Delete" permission, or that the item is checked out by another user. Another common question: "You need to give a contractor access to only one folder within a document library, while preventing them from seeing other folders. How do you achieve this?" The correct approach is to break permission inheritance on that folder and grant the contractor appropriate permissions.

Troubleshooting questions test your diagnostic skills. For example: "Users cannot upload files larger than 250 MB to a SharePoint site. The global administrator confirms no tenant-level restrictions. What should you check?" The answer would be the file upload limit set on the specific site collection or the web application (in on-premises). Another question: "A SharePoint site is running slowly. Users in the same region complain about page load times. What is the most likely cause?" Possible answers include excessive customizations, large lists with too many items (list view threshold), or insufficient server resources.

Integration questions appear in exams like MS-700 and PL-900. For example: "When a user creates a new team in Microsoft Teams, what Microsoft 365 resource is automatically created behind the scenes?" The answer is a SharePoint team site and a corresponding document library in the site. Another: "You want to trigger a Power Automate flow when a new file is added to a SharePoint document library. Which trigger should you select?" The answer is "When a file is created or modified (properties only)" from the SharePoint connector.

By understanding these question patterns, you can focus your study on practical administration tasks, permission hierarchies, and integration points, all of which are heavily tested on certification exams.

## Example scenario

You are an IT support specialist for a mid-sized company called Northwind Traders. The sales team wants a SharePoint site to organize their proposals, contracts, and meeting notes. They have 25 members, and the team lead, Sarah, wants to control who can edit documents. The company uses Microsoft 365 Business Premium.

First, you open the SharePoint Admin Center in your browser and create a new site collection. You choose the Team site template because the sales team needs a shared workspace for collaboration. You name the site "Sales Hub" and set the URL to https://northwind.sharepoint.com/sites/SalesHub. You add Sarah as the primary site collection administrator and yourself as a secondary admin. You set the storage limit to 50 GB because the team expects to upload large proposal files.

Once the site is created, you navigate to it and see the default document library called "Documents." Sarah asks that only the five senior sales managers should be able to edit the proposals folder inside this library, while the other 20 sales reps should only be able to read it. You break permission inheritance on the "Proposals" folder. You create a SharePoint group called "Sales Managers" and give it "Contribute" permission on the folder. The default "Members" group already has "Edit" access to the whole library, so you remove their inherited permissions on the folder and leave them with only "Read" access.

Next, you notice that the team wants a shared calendar for tracking client meetings. You go to "Site Contents" and click "Add an app." You select the "Calendar" app and name it "Client Meetings." You also create a custom list called "Leads" to track potential deals. For each lead, you add columns like "Company Name," "Contact Person," "Estimated Value," and "Stage (New/In Progress/Closed Won)." You use a choice column for the "Stage" field to ensure consistency.

Finally, you enable versioning on the document library so that every time someone edits a document, the old version is saved. You set the retention to keep the last 10 major versions. You also configure a workflow (using Power Automate) that sends an email to Sarah whenever a new contract is uploaded to the "Contracts" folder. The sales team now has a complete collaboration hub that meets their needs, and Sarah can manage her team's content without needing IT help every time.

## Common mistakes

- **Mistake:** Confusing a SharePoint site with a SharePoint website or public web page.
  - Why it is wrong: A SharePoint site is an internal collaboration space within an organization, not a public website. It requires authentication and is typically not accessible to external users unless explicitly shared. Learners often think any SharePoint page is like a public webpage, which leads to incorrect assumptions about security and accessibility.
  - Fix: Remember that a SharePoint site is an intranet site for your organization. It is private by default. If you need a public-facing website, you would use a different tool like WordPress or a dedicated web hosting service, not SharePoint.
- **Mistake:** Assuming all SharePoint sites are the same and can be used interchangeably.
  - Why it is wrong: SharePoint offers different site templates (Team site, Communication site, Publishing site) each designed for specific purposes. Using the wrong template can lead to missing features or poor user experience. For example, a Communication site lacks the Microsoft Teams integration and group calendar that a Team site provides.
  - Fix: When creating a site, match the template to the need. Use a Team site when the team needs shared document libraries, lists, and integration with Planner and Outlook. Use a Communication site for broadcasting news and information to a broad audience without requiring membership.
- **Mistake:** Neglecting to configure permission inheritance properly.
  - Why it is wrong: By default, a SharePoint site inherits permissions from its parent, which may lead to security loopholes. For example, if you do not break inheritance on a sensitive document library, all site members may have edit access to it. This mistake can result in data leaks or accidental modifications.
  - Fix: Always break permission inheritance on containers (sites, lists, folders) that need unique access permissions. After breaking inheritance, remove any inherited groups and add only the required users or groups with appropriate permission levels (Read, Contribute, Edit, Full Control).
- **Mistake:** Overlooking versioning settings and deletion recovery.
  - Why it is wrong: Without versioning enabled, there is no way to recover a previous version of a document if someone overwrites or deletes content. Many learners assume SharePoint automatically keeps all versions, but the default may be limited or disabled. This can lead to permanent data loss.
  - Fix: Enable major versioning on document libraries, especially those storing important files. Set the number of versions to keep based on your organization’s retention policy. Also, ensure the recycle bin is configured (two-stage recycle bin in SharePoint) for accidental deletions.
- **Mistake:** Thinking that SharePoint sites can be used offline without any configuration.
  - Why it is wrong: SharePoint sites are primarily online. While you can sync files to your computer via OneDrive sync or SharePoint sync, this requires the OneDrive sync client and proper network access. Offline access is limited to files you have manually synced. Learners often try to access the entire site offline and get confused.
  - Fix: Educate users that SharePoint sites are web-based. If offline access is needed, guide them to sync specific document libraries using the OneDrive sync app. For full offline functionality, consider using SharePoint Server (on-premises) with a VPN, but even then the web interface requires a connection.

## Exam trap

{"trap":"On an exam, you are asked: 'A user wants to share a document from a SharePoint site with an external vendor. Which permission level must the user have at minimum?' The answer choices include 'Read,' 'Contribute,' 'Edit,' and 'Full Control.' Learners often pick 'Read' because they think read access allows sharing, but 'Read' does not include the 'Share' permission.","why_learners_choose_it":"Learners may confuse the ability to view an item with the ability to share it. In many platforms, view access often implies you can share a link. However, in SharePoint, the 'Share' permission is part of the 'Contribute' level and above. 'Read' only allows viewing, not sharing.","how_to_avoid_it":"Remember that in SharePoint, you need at least 'Contribute' permission (or a custom permission level that includes 'Share') to share a document or site with others. Always check the specific permission level's capabilities. Review the official SharePoint permission levels: Read, Contribute, Edit, and Full Control, noting that 'Contribute' includes 'View, add, update, delete, and share.'"}

## Commonly confused with

- **SharePoint site vs Microsoft Teams (Team):** While a SharePoint Team site is closely integrated with Microsoft Teams, they are not the same. A Microsoft Team is a chat-based workspace with channels that link to a SharePoint site for file storage. The SharePoint site provides document libraries, lists, and permissions, while Teams provides persistent chat, meetings, and apps. Think of the SharePoint site as the file cabinet and the Team as the conversation hub. (Example: You create a Team called 'Marketing Team' in Microsoft Teams. Behind the scenes, a SharePoint site called 'Marketing Team' is automatically created. When you upload a file in the Teams Files tab, it is stored in the SharePoint site's document library. But the conversation history and meeting recordings live in Teams, not SharePoint.)
- **SharePoint site vs OneDrive for Business:** OneDrive for Business is a personal cloud storage library for an individual user, while a SharePoint site is a shared workspace for a group. OneDrive gives you a private space to store your own documents, though you can share them. SharePoint sites are designed for team-wide content and collaboration. OneDrive is often integrated with SharePoint for file sync, but they serve different purposes. (Example: You store your personal expense reports in your OneDrive. Your team’s project plan is stored in the team’s SharePoint site. You can grant your manager access to your OneDrive document, but the project plan in SharePoint is automatically accessible to all team members with appropriate permissions.)
- **SharePoint site vs SharePoint Online (Tenant):** A SharePoint site is a single container within a much larger entity called the SharePoint Online tenant. The tenant is the entire SharePoint environment for your organization, including all site collections, global settings, storage quotas, and administration. A site is like one folder in a big filing cabinet, while the tenant is the entire cabinet and the room it is in. (Example: Your company 'Contoso' has a SharePoint Online tenant at contoso.sharepoint.com. Within that tenant, you create a site for the Marketing department (contoso.sharepoint.com/sites/Marketing) and a separate site for the HR department (contoso.sharepoint.com/sites/HR). Both are sites within the same tenant.)
- **SharePoint site vs SharePoint List:** A SharePoint list is a component inside a SharePoint site that holds structured data (like a spreadsheet). The site itself is the whole container that can contain many lists, libraries, pages, and other features. Confusing the two is like mistaking a single file cabinet drawer for the entire office. (Example: Within your project SharePoint site, you have a list called 'Tasks' that tracks action items. That list is one app inside the site. The site also has a document library called 'Documents' and a calendar. The site is the collection of all these apps.)

## Step-by-step breakdown

1. **Planning the Site Structure** — Before creating a SharePoint site, determine its purpose, audience, and content. Decide whether it will be a Team site (for collaboration with group members) or a Communication site (for broadcasting information). Identify the top-level navigation and whether you need subsites. This step affects permissions, storage, and discoverability.
2. **Provisioning the Site Collection** — In the SharePoint Admin Center (or via PowerShell for automation), create a new site collection. Choose the appropriate template, enter a title and URL, assign primary and secondary administrators, and set the storage quota. This step creates the underlying database and initial site structure.
3. **Configuring Site Permissions** — By default, the site inherits permissions from the parent (if any) or uses the default SharePoint groups (Owners, Members, Visitors). Adjust permissions by adding users or security groups. If needed, break permission inheritance on specific libraries or lists to grant unique access. This controls who can view, edit, or manage content.
4. **Adding and Configuring Apps (Libraries and Lists)** — From the site contents page, add apps such as a Document Library, Calendar, Tasks list, or custom list. Configure each app with appropriate columns, views, versioning, and validation. For example, set up metadata columns on a document library to enable filtering and search. This step builds the functional components of the site.
5. **Customizing the Site Look and Navigation** — Use the site settings to change the theme, logo, and description. Set up left navigation or top link bar to help users find content quickly. Add web parts to the home page, such as a news feed, document library preview, or calendar. This makes the site user-friendly and visually consistent with company branding.
6. **Enabling Features and Integrations** — Activate site features like Publishing (for rich pages), Content Organizer (for routing documents), or SharePoint Server Enterprise Site Collection features (for advanced search). Connect the site to Microsoft Teams, Power Automate, or Power BI if needed. This step extends the site's capabilities beyond the default.
7. **Testing and Deploying to Users** — Before rolling out the site to the whole team, test it with a small group of stakeholders. Check permissions, upload a few documents, create sample list items, and verify that links work. Gather feedback and make adjustments. Then communicate the site URL and training materials to the intended audience.

## Practical mini-lesson

A SharePoint site is not just a container; it is a dynamic environment that requires careful planning and ongoing management. As an IT professional, you need to understand the lifecycle of a SharePoint site, from creation to eventual archiving. Here is what you need to know to manage them effectively in practice.

First, always plan the site hierarchy. In a large organization, you might have site collections for each department and subsites for projects. However, excessive nesting can complicate navigation and permissions. Best practice is to keep the hierarchy flat, use site collections for major divisions and avoid deep subsite structures unless absolutely necessary. Each site collection has its own set of permissions and content database, which improves performance and manageability.

Second, storage management is critical. SharePoint Online sites have tenant-level storage limits. You can set per-site storage quotas to ensure one department does not consume all the storage. Monitor storage usage in the SharePoint Admin Center. If a site approaches its limit, you can increase the quota (if tenant storage is available) or archive large files to a separate location. On-premises SharePoint requires you to monitor content database sizes to stay within SQL Server limits.

Third, permission management is often the most complex task. Avoid giving users Full Control unless they are site collection administrators. Use SharePoint groups instead of individual permissions. The built-in groups, Owners, Members, Visitors, cover most needs. For advanced scenarios, create custom permission levels that combine specific rights. For example, create a "Read and Share" level for external partners. Remember that permission inheritance is a powerful tool but can cause confusion when accidentally broken. Always document where inheritance is broken.

Fourth, versioning and retention policies should be configured early. Document library versioning keeps a history of changes, which is invaluable for auditing and recovery. Set retention labels and policies using Microsoft 365 compliance center to automatically delete or preserve content after a specified period. This helps organizations meet legal and regulatory requirements.

Fifth, governance is key. Establish a site creation policy: who can create sites, what naming conventions to use, and what templates are allowed. In SharePoint Online, you can use site creation policies and custom forms to enforce these rules. Without governance, you risk site sprawl, hundreds of unused sites consuming storage and confusing users. Use site collection analytics to identify inactive sites and delete or archive them.

Finally, troubleshooting common issues: users may report that they cannot access a site even though they are members. Check permission inheritance at the site level, and also verify that the user is not blocked from the site via a security group membership issue. Another frequent issue is slow site performance. Check list view thresholds (default 5,000 items) and consider indexing columns if users filter large lists. Also, review custom scripts and web parts that might cause rendering delays. By mastering these practical aspects, you will be able to manage SharePoint sites confidently in any IT environment.

## Memory tip

Think of a SharePoint site as a shared digital room: you need a key (permissions), you put files in the right drawer (library), you can only take files out (view) or edit them based on your key's level.

## FAQ

**What is the difference between a SharePoint site and a SharePoint page?**

A SharePoint site is the overall container that holds multiple pages, libraries, lists, and settings. A SharePoint page is a single web page within that site that displays content using web parts. Think of the site as a whole house and a page as one room in the house.

**Can I create a SharePoint site without being an administrator?**

In SharePoint Online, if your organization allows self-service site creation, users with appropriate permissions can create sites from the SharePoint home page. However, site collection creation may require global admin or SharePoint admin privileges. Check your organization’s policy.

**How do I delete a SharePoint site?**

In SharePoint Online, go to the SharePoint Admin Center, select the site, and choose 'Delete.' The site goes to the first-stage recycle bin and then to the second-stage recycle bin before permanent deletion after 93 days. Site collection administrators can also delete a site from within the site by going to Site Settings and then 'Delete this site.'

**What is the default storage limit for a SharePoint site?**

In SharePoint Online, each site collection has a default storage limit of 25 GB, but the tenant administrator can increase this up to the tenant’s total storage allocation. On-premises SharePoint storage depends on the content database size configured by the farm administrator.

**Can I move a SharePoint site from one tenant to another?**

SharePoint sites cannot be directly moved between tenants. However, you can migrate content using third-party tools or Microsoft’s Migration Manager, which supports moving files and lists from one tenant to another. The site structure and permissions may need to be recreated.

**Do I need a Microsoft 365 license to access a SharePoint site?**

Yes, each user who needs to access SharePoint Online must have a valid Microsoft 365 license that includes SharePoint Online (such as Business Basic, Business Standard, or Enterprise plans). External users can be invited as guests and require a license if they need more than view access in some configurations.

**What is a site collection versus a site?**

A site collection is a top-level container that holds one or more sites. It has its own set of permissions, features, and a content database. A site is a single website within that collection. For example, you might have a site collection for the HR department, with a subsite for Recruiting and another for Benefits.

## Summary

A SharePoint site is a web-based collaboration space within Microsoft SharePoint that serves as a central hub for teams to store, manage, and share content. It is a fundamental concept in Microsoft 365 collaboration, appearing on multiple certification exams, including MS-900, MS-102, and the SharePoint Administrator Associate exam. Understanding SharePoint sites involves knowing the different site templates (Team site vs. Communication site), how to provision and configure them, how to manage permissions and storage, and how to integrate them with other Microsoft 365 services like Teams and Power Platform.

For IT certification candidates, mastering SharePoint sites is essential because questions often test your ability to match site types to business needs, configure permissions, troubleshoot access issues, and administer site settings. Common mistakes include confusing SharePoint sites with other services, misapplying permissions, and underestimating the importance of versioning and governance. Real-world practice, such as creating test sites in a Microsoft 365 development tenant, will solidify your understanding and prepare you for exam scenarios.

The exam takeaway: Whenever you see a question about collaboration, document management, or intranet, think 'SharePoint site.' Know the key features of each template, the default permission levels, the admin tools, and the integration points. With this knowledge, you will be able to tackle both conceptual and configuration questions confidently.

---

Practice questions and the full interactive page: https://courseiva.com/glossary/sharepoint-site