PNP PowerShell Integration

Our PowerShell code snippets uses the PNP PowerShell module. For a deeper understanding of its functionality, please visit the PNP PowerShell GitHub page.

Tenant Properties

SharePoint Online web parts can access tenant properties using the rest API. They don’t require specific API permissions and can be read and set if the user can contribute to the site where the property is set. They can currently only be configured via PowerShell (SPO Management or PNP). Our snippets use PNP because it requires minimal privileges, making them the easiest to use in a lot of cases. To learn more about tenant properties in PowerShell, read this Microsoft documentation.

App Catalog

The web part searches for tenant properties within the current site. While tenant properties can be set on any site, using the AppCatalog ensures availability on any site within the tenant: the property will be made available out to all sites. Adding a property to a single site (that is not an app catalog) will only make it only available to that site. Learn more about configuring and using the App Catalog here.


The Badger365 FAQ web part is designedfor use in SharePoint Online. We don’t support other SharePoint versions.

Web Part Functionality in Microsoft Teams

The FAQ web part works in Teams as a tab added through a modern SharePoint page, but must be configured on SharePoint

Validation messages

Each instance of the Badger365 FAQ web part must be validated individually. To see the current validation status of a web part, open the web part properties and browse to page 3.

Auto-validation failed. SaaS subscription not found.
The web part couldn’t find the tenant property Badger365-FAQ. This is the normal response when trying out the FAQ web part or when the web part is validated when the tenant property is not created.


Use the button below to validate this web part manually
This message appears when auto validation failed previously and the page was reloaded. If you have acquired a subscription id in the meantime and set it as a tenant property, use the ‘Validate’ button to trigger the validation process manually


  • Click the Validate button to start the validation manually

Auto-validation failed. The submitted subscription ID did not return a result. The submitted Subscription Id was <guid>
A tenant property was found and it contains a valid GUID but it’s not a valid subscription Id for your teant.


Check your SaaS registration details in the Azure Portal

  • Open the  Azure Portal
  • Search for Saas and open your subscription
  • click on the link Open SaaS Account on publisher’s site to find your subscription details

Auto-validation failed. Tenant property ‘Badger365-FAQ’ exists but does not contain a valid GUID

Something went wrong creating the tenant property. The value must be a valid guid, and can not contain any other text, special characters or lead spaces


  • Use snippet 2 on the validation page to retrieve the value of the subscription ID
  • Compare it with the provided subscription ID

Auto-validation failed. The returned status is: <status>. The submitted Subscription Id was <guid>.

The subscription is only valid when the returned status is Subscribed. Any other status will render the above message.


Check your SaaS registration details in the Azure Portal

  • Open the  Azure Portal
  • Search for Saas and open your subscription
  • Review the details of the subscription

Auto validation failed. SaaS application is not configured correctly

This error will show if you have configured a tenant property but the SaaS subscription is not configured. The tenant property was configured correctly, but the SaaS registration client that communicates with the Marketplace was not found or is inaccessable.

  • Open the Badger365 SaaS page
  • Make sure the configuration is set up correctly