You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are running the below commands to pull back site details and as enviroment is growing, the commands takes longer and longed to run. Is there a way to reduce the time it takes to run both these commands, or is there a date field we can look at to see if we need to even query the site all.
But to get the further details that is not returned from the first cmdlet, we have to loop each site from the previous output and fetch the following information
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
We are running the below commands to pull back site details and as enviroment is growing, the commands takes longer and longed to run. Is there a way to reduce the time it takes to run both these commands, or is there a date field we can look at to see if we need to even query the site all.
$SPOSites = Get-PnPTenantSite |select Title,Status,ResourceUsageCurrent,StorageUsage,Url,Owner,StorageMaximumLevel,StorageWarningLevel,ResourceQuota,ResourceQuotaWarningLevel,Template,PWAEnabled,SharingCapability,SiteDefinedSharingCapability,GroupID,RelatedGroupId,TimeZoneId,HubSiteId,IsHubSite
But to get the further details that is not returned from the first cmdlet, we have to loop each site from the previous output and fetch the following information
$MissingAttribute = Get-PnPTenantSite -Url $SPOSite.Url | select Url,GroupId,HubSiteId,IsHubSite,TimeZoneId,RelatedGroupId
Beta Was this translation helpful? Give feedback.
All reactions