The process of building custom applications and tools that interact with Microsoft SharePoint, including SharePoint Online in Microsoft 365.
Hi,
Your observation is consistent with the currently documented Microsoft Purview Audit schema.
Microsoft documents SiteCollectionCreated as an operation generated when a new SharePoint site collection is created or a user’s OneDrive site is provisioned. Microsoft also notes that creating a Microsoft 365 group or team can generate a site-collection creation record. However, the current Audit log activities reference does not list a SubsiteCreated or WebCreated operation.
A SharePoint subsite is a child web within an existing site collection. Its creation is not documented as being covered by SiteCollectionCreated, and there is no other documented Unified Audit Log operation that can be treated as an equivalent subsite-creation event.
This does not mean that activity within a subsite is excluded from auditing. Subsequent file, list, sharing, or permission events may contain the subsite URL in properties such as SiteUrl or ObjectId. However, these events only show that an action occurred in that subsite. They do not establish when the subsite was created. Using the earliest available activity as a proxy would therefore be incomplete and unreliable.
Consequently, Purview Audit data alone cannot reliably provide a historical list of newly created subsites, including nested subsites.
For subsites that still exist, GET /sites/{site-id}/sites can be queried recursively, and the returned site resource includes createdDateTime. This is current site metadata rather than an audit event and cannot identify subsites that have already been deleted.
For future change tracking without performing a full enumeration each time, /sites/delta can be used and the returned changes stored externally. That history would be maintained by the application rather than being Microsoft Purview audit data.