User Profile
reshmeeauckloo
Brass Contributor
Joined 5 years ago
User Widgets
Recent Discussions
Re: Issue with get-sposite SPO PowerShell
Unfortunately the MS case got closed as SPO PowerShell scripting was not supported by the support team. The only way to get the correct properties is to iterate through each site ``` $sites = Get-SPOSite -Limit All | Select-Object -Property Url $siteArray = @(); foreach($site in $sites) { $siteProp = Get-SPOSite -Identity $site.Url $siteArray+=$siteProp } $siteArray | Select-Object -Property *525Views0likes0CommentsIssue with get-sposite SPO PowerShell
Issue with SPO PowerShell get-sposite for all sites not returning the correct values for different properties SharingDomainRestrictionMode , LimitedAccessFileType, DefaultSharingLinkType, DefaultLinkPermission etc, If get-sposite -Identity <siteurl> is used, the correct values for the properties are returned. It seems to be an issue with the underlying CSOM. Can someone at Microsoft help with this? I have raised case #2405120050000021 for this. My previous experience raising a case related to SPO PowerShell was closed because SPO PowerShell was not supported by the team handling the case.Solved584Views0likes3CommentsRe: Get-SPOTenantServicePrincipalPermissionGrants unknown error
Thanks everyone who have read my post. After going in circles with one Ms case case closed without resolution because PowerShell script is out of scope, finally got it escalated with a second case and it will be fixed soon.591Views0likes3CommentsRe: Searchable columns link missing
I have raised a ticket with Microsoft as well, the documentation on https://learn.microsoft.com/en-us/sharepoint/make-site-content-searchable does not mention about it being an exclusive on premises feature. I will update the ticket once I hear more from Microsoft.444Views0likes0CommentsSearchable columns link missing
Can't see the link Searchable columns under site settings as described in link to exclude columns. https://learn.microsoft.com/en-us/sharepoint/make-site-content-searchable Even running PnP PowerShell to update the settings of the NoCrawl of the field throws an error. Is it possible to make a column non searchable?516Views0likes2Comments"Add Group Owners as site admin" button is used from SharePoint Admin Centre
When "Add Group Owners as site admin" button is used from SharePoint Admin Centre to add the M365 group owners as site admin , the owners group is made visible. add-o365-group-owner-to-site-collection-administration-list The M365 group owners are added as hidden principal within the connected SharePoint site on site creation. However if site owners are removed from the site admins and added back, The owners group is visible when previously it was hidden The owners group is visible which is different from how it was originally set up with the group being hidden. Anyway to make the owners group visible464Views0likes0CommentsRe: Why have group owners full control in the SharePoint teamsite
The group owners are added as hidden principal http://[https://learn.microsoft.com/en-us/sharepoint/dev/transform/modernize-connect-to-office365-group-permissions](https://learn.microsoft.com/en-us/sharepoint/dev/transform/modernize-connect-to-office365-group-permissions?wt.mc_id=MVP_308367)1.1KViews0likes0CommentsRe: Unable to run set-sposite -Disablesharingfornonowners
Yeah I did raise it with PnP PowerShell and we agreed it is something with SP CSOM and closed the ticket. I need to try it with the latest nightly build before raising it back again if it is still an issue. Thanks very much for your help on this ganeshsanap.1.3KViews0likes0CommentsUnable to run set-sposite -Disablesharingfornonowners
Running the SPO PowerShell ```PowerShell $AdminSiteURL= "https://reshmeeauckloo-admin.sharepoint.com" $SiteURL= "https://reshmeeauckloo.sharepoint.com/sites/testclone2" #Connect to SharePoint Online services Connect-SPOService -url $AdminSiteURL #Disable Sharing for Non-Owners Set-SPOSite -Identity $SiteURL -DisableSharingForNonOwners ``` set-pnpsite -Disablesharingfornonowners Set-PnPSite: The type of data at position 3330 is different than the one expected.1.7KViews0likes8CommentsRe: Delete Redirect sites from a renamed tenant
The redirect for the root site and my site was accidentally deleted first before the rest of the redirects were removed. It is an expected behaviour by design and Ms will recreate the redirect for the root site and my site and I will test deletion of redirect sites excluding the root site.1KViews0likes0CommentsDelete Redirect sites from a renamed tenant
After a tenant rename, redirect sites have been created for every existing sites prior to the tenant rename. However these are causing issues with a third party backup solution which is unable to filter out those redirect sites. Running the cmdlet Remove-SPOSite -Identity https://[oldDomainName].com/sites/housestuff throws the error Remove-SPOSite : The site url https://[oldDomainName].com/sites/housestuff does not reference a domain in this tenant. Accessing https://[oldDomainName].com/sites/housestuff from the browser redirects to the new domain https://[oldDomainName].com/sites/housestuff correctly. Any help or advice will be appreciated.1.1KViews0likes1Comment
Recent Blog Articles
No content to show