Skip to content

Storage

EnvironmentStorage account
Developmentstproven2uksdev001
Teststproven2ukstest001
Productionstproven2uksprod001

Provisioning templates are stored in the pnp-templates blob container. These are sorted hierarchically into a tenant_id/template_name. A tenant ID may be either a GUID or a domain name.

Each template consists of a template.xml file containing the PnP Provisoning template, a hubContentTypes.json file containing the content types to be synced from the hub, and then any included files with their structure preserved alongside.

The below tree shows an example of what this may look like.

  • Directoryb2b8a771-e4ce-4a15-a6fb-a19e8d195a76
    • Directorymy-template
      • template.xml
      • hubContentTypes.json
      • DirectoryShared Documents
        • Lorem Ipsum.docx
        • DirectoryImages
          • MyPicture.png
  • Directorycore365dev.onmicrosoft.com
    • Directoryanother-template
      • template.xml
      • hubContentTypes.json

Alongside the system-managed tables, there are three custom ones used across the solution:

  • Jobs - Tracks a list of every job that has run. This keeps the durable functions ID to allow it to be looked up.
  • Templates - Tracks a list of used templates and metadata about their generation.
  • Tenants - Tracks a list of tenants which have ProvEn installed.