Active Sites Export Misses Recent Sites: Admin Checklist

When you export the list of active sites from the SharePoint admin center, you may notice that recently created or modified sites do not appear in the CSV file. This happens because the export tool captures a snapshot of site data at a specific moment, and sites that have not yet been fully indexed or committed to the database are omitted. This article explains why recent sites go missing from the export, provides a step-by-step checklist to verify and retrieve them, and outlines related failure patterns to watch for.

Why Recent Sites Are Missing from the Active Sites Export

The Active Sites page in the SharePoint admin center displays sites that have been fully provisioned and indexed. When you click Export, the system generates a CSV file based on the current index state. Sites that were created or modified within the last 15 to 30 minutes may not yet appear in that index. This latency is by design: the SharePoint indexing service processes changes in batches to reduce load on the database. Additionally, the export does not include sites that are still in a provisioning state, such as a site whose creation was triggered but not completed. The same applies to sites that were recently restored from the recycle bin or migrated from another tenant.

Indexing Delay and Provisioning State

When a user creates a new site, the provisioning process must finish before the site appears in the admin center. After provisioning, the indexing service must pick up the site metadata. If you export before both steps complete, the site will be missing from the CSV. The typical delay ranges from 15 minutes to one hour, depending on tenant load and region.

Filter and Paging Limitations

The admin center UI uses server-side paging. If you apply a filter that includes recent sites but your export request is processed before the filter query returns the latest results, the export will still omit those sites. The export function does not re-query the index after the initial page load.

Checklist to Verify and Retrieve Missing Sites

Follow these steps to confirm whether recent sites are truly missing or simply delayed, and to retrieve them using alternative methods.

1. Confirm the site URL and creation time
   Ask the site owner or creator for the exact site URL and the time it was created or last modified. If the site was created less than 30 minutes ago, wait 30 minutes and then refresh the Active Sites page before exporting again.
2. Apply a date-range filter before exporting
   In the SharePoint admin center, go to Active sites. Click the filter icon and select Last modified. Choose a custom date range that includes the recent time period. Click Apply, then click Export. The filter forces the system to query the latest index for that range.
3. Export from the Sites page using Microsoft 365 admin center
   Open the Microsoft 365 admin center at admin.microsoft.com. Go to Show all > Admin centers > SharePoint. Alternatively, use the direct URL: admin.microsoft.com/Adminportal/Home#/sharepoint. Navigate to Active sites, apply the same filter, and export. This method sometimes bypasses a stale cache in the SharePoint admin center.
4. Retrieve all sites with PowerShell
   Install the SharePoint Online Management Shell if you have not already. Run the following command to export all sites, including recent ones:
   Get-SPOSite -IncludePersonalSite $false | Export-Csv -Path "C:\temp\all-sites.csv" -NoTypeInformation
   This command queries the SharePoint Online database directly and does not rely on the admin center index. To target sites created in the last 24 hours, use a filter:
   Get-SPOSite -IncludePersonalSite $false | Where-Object {$_.LastContentModifiedDate -ge (Get-Date).AddDays(-1)} | Export-Csv -Path "C:\temp\recent-sites.csv" -NoTypeInformation
5. Check the site collection audit log
   If the site still does not appear in any export, review the audit log in the SharePoint admin center. Go to Audit > Audit log. Search for “Site created” or “Site modified” events. This confirms whether the site was provisioned and when. If no audit event exists, the site may have failed provisioning.
6. Run a site health check
   Use the SharePoint admin center > Site health page to check for sites with provisioning errors. If the site shows a “Provisioning incomplete” status, wait for the process to finish or contact Microsoft Support.

If the Active Sites Export Still Misses Recent Sites

Even after following the checklist, you may still encounter missing sites. Below are the most common additional scenarios and their fixes.

Site was created but never indexed

A site can be fully provisioned yet never indexed if the provisioning process encountered a non-critical error. To force indexing, navigate to the site directly using its URL. Open the site settings, make a small change such as updating the site description, and save. This triggers a re-index. Wait 15 minutes and run the export again.

Site was deleted and re-created

If a site was deleted and a new site with the same URL was created, the old site record may still appear in the export while the new one is missing. Check the site ID in the export CSV. The ID should match the current site. If it does not, run Get-SPOSite -Identity in PowerShell to confirm the correct site ID, then re-export using the PowerShell method.

Site is in a different geo location

For multi-geo tenants, the Active Sites page shows only sites in the default geo location. Sites created in a satellite location will not appear in the default export. Switch to the correct geo location in the admin center by selecting the location drop-down, or use PowerShell with the -IncludePersonalSite $false parameter, which returns sites from all geo locations.

Active Sites Export vs PowerShell Export: Key Differences

Item	Admin Center Export (CSV)	PowerShell Get-SPOSite
Data source	Indexed snapshot from the admin center UI	Direct database query via SharePoint Online Management Shell
Latency	15–60 minutes for recent sites to appear	Near real-time; returns sites as soon as provisioning completes
Filtering options	Date range, site type, and template filters available in UI	Any property filterable via Where-Object, including LastContentModifiedDate, StorageUsage, and Owner
Geo-location support	Shows only the selected geo location	Returns sites from all geo locations by default
Personal sites	Excluded by default	Excluded with -IncludePersonalSite $false; included if set to $true

Use the admin center export for a quick, filtered view of indexed sites. Use PowerShell when you need a complete, up-to-date list that includes recent sites, multi-geo sites, or custom property filters. To automate the PowerShell export, schedule the script as a task using Azure Automation or a Windows Task Scheduler job that runs daily.