Great news:
Added -Interactive login option to Connect-PnPOnline which is similar to -UseWebLogin but without the limitations of the latter. The -UseWebLogin is using cookie based authentication towards SharePoint and cannot access Graph tokens. Using -Interactive we use Azure AD Authentication and as a result we are able to acquire Graph tokens.
more changes: https://github.com/pnp/powershell/releases/tag/1.3.0
Recently I came across this small business company – akTeams. Nice people. What they do is Microsoft 365 and Microsoft Teams – support, setup, licensing. I recommend.
OnNew:
Set(SharePointFormMode, “NewForm”); NewForm(formNew); Navigate(screenNew, ScreenTransition.None)
OnEdit:
Set(SharePointFormMode, “EditForm”); EditForm(formEdit); Navigate(screenEdit, ScreenTransition.None)
OnView:
Set(SharePointFormMode, “ViewForm”); ViewForm(formView); Navigate(screenView, ScreenTransition.None)
OnSave – If(SharePointFormMode=”CreateForm”, SubmitForm(CreateItemForm), If(SharePointFormMode=”EditForm”, SubmitForm(EditItemForm)))
OnCancel – If(SharePointFormMode=”CreateForm”, ResetForm(CreateItemForm), If(SharePointFormMode=”EditForm”, ResetForm(EditItemForm)))
Works (tested) for PowerShell 7 and PnP.PowerShell 1.3.0
# cert stored in KeyVault
$orgName = "orgname" #
$tenant = "$orgName.onmicrosoft.com"
$adminUrl = "https://$orgName-admin.sharepoint.com"
$clientID = "" # Client ID
$VaultName = 'AutomationVaultName'
$certName = 'CertificateName'
$secretSecureString = Get-AzKeyVaultSecret -VaultName $vaultName -Name $certName
$secretPlainText = ConvertFrom-SecureString -AsPlainText -SecureString
Connect-PnPOnline -Url $adminUrl -ClientId $clientID -CertificateBase64Encoded $secretPlainText -Tenant $tenant Based on:
As an Office 365 administrator, I would like to get some reports on Yammer with PowerShell. How it’s done?
Patrick Lamber wrote a good article here: “Access the Yammer REST API through PowerShell“. The only I would add (important!) is:
By default, even with a Verified Admin token, you do not have access to private messages and private groups content.
To get private stuff, you need select “Private Content Mode” under Yammer Admin Center -> Content and Security -> Content Mode:
Check Microsoft: “Monitor private content in Yammer” and
Yammer: “Verified Admin Private Content Mode“
If you do not have “Private Content Mode” set up, you might see some weird “Invoke-WebRequest” errors like:
(WIP)
Can I run something like
$items | ForEach-Object -Parallel {
$listItem = Set-PnPListItem -List "LargeList" -Identity $_ -Values @{"Number" = $(Get-Random -Minimum 100 -Maximum 200 ) }
} Unfortunately, no. Instead, use batching!
$batch = New-PnPBatch
1..100 | ForEach-Object{ Add-PnPListItem -List "ItemTest" -Values @{"Title"="Test Item Batched $_"} -Batch $batch }
Invoke-PnPBatch -Batch $batchMore:
– Batching in PnP PowerShell | PnP PowerShell
– https://www.youtube.com/watch?v=0-DSwZyK2Zo
(WIP)
PowerShell is our best friend when it comes to ad-hoc and/or scheduled reports in Microsoft 365. PnP team is doing great job providing more and more functionality with PnP PowerShell module for Office 365 SharePoint and Teams.
Small and medium business organizations are mostly good, but for large companies it might be a problem due to just huge amount of data stored in SharePoint. PowerShell reports on all users or all sites might run days… which is probably OK if you run this report once, but totally not acceptable if you need this report e.g. daily/weekly or on-demand.
How can we make heavy PowerShell scripts run faster?
Of course, you start with logic (algorithm) and leveraging full PowerShell functionality (e.g. PowerShell 7 parallelism or PnP batching).
(examples)
What if you did everything, but it still takes too long? You need something like brute force – the closer your code runs to your tenant – the better.
What are the option?
– Automation account runbook (+workflow)
– Azure Function Apps
– Azure VM in the region closest to your Tenant
Seemed like a good option, but not something Microsoft promotes. Even opposite – automation accounts support only PowerShell 5 (not 7), no plug-ins for VS Code and recently there were messages on some retirement or smth.
Meantime, I tested it – and did not find any significant increasing in speed. In a nutshell, what is behind this service? Same windows machines running somewhere in Azure .
TBC
References
– PnP PowerShell
Microsoft: “Using modern pages in Microsoft SharePoint is a great way to share ideas using images, Office files, video, and more. Users can Add a page to a site quickly and easily, and modern pages look great on any device.
If you’re a global or SharePoint admin in Microsoft 365, you can allow or prevent users from creating modern pages. You can do this at the organization level by changing settings in the SharePoint admin center. If you allow the creation of site pages as the organization level, site owners can turn it on or off at the site level.“
By default both
– Allow users to create new modern pages
– Allow commenting on modern pages
are turned on (enabled)
Tenant or SharePoint admin can find settings under
SharePoint Admin Center -> Settings -> Pages
How it looks like:
Site Pages are created under “Pages” Library.
Let us test it, with:
– (tenant-level) Allow users to create new modern pages: ON
– (tenant-level) Allow commenting on modern pages: ON
– web feature “Site Pages” – “Allows users to add new site pages to a site”: Activated
| User Permissions | can create Page | can edit page | can Enable/Disable page comments | can comment on Page |
| Full Control (Owner) | Yes | Yes | Yes | Yes |
| Edit (Member) | Yes | Yes | Yes | Yes |
| Read (Visitor) | No | No | No | Yes |
There is a web feature “Site Pages” – “Allows users to add new site pages to a site”.
The feature is activated by default:
What if we disable this feature?
“New -> Page” has disappeared from “New” menu under “Site Contents” for Owners and Members…
From “Home” and “Pages” you still can see “New -> Page” options.
You can still create a new page from but if you try to create a page from Pages – “Sorry, something went wrong” “Cannot create a Site Page. Please have your administrator enable the required feature on this site.” :
Office 365 behavior, with:
– (tenant-level) Allow users to create new modern pages: ON
– (tenant-level) Allow commenting on modern pages: ON
– web feature “Site Pages” – “Allows users to add new site pages to a site”: Deactivated
| User Permissions | can create Page | can edit page | can Enable/Disable page comments | can comment on Page |
| Full Control (Owner) | Yes, but only from “Home” not from “Site Contents” or “Pages” | Yes | Yes | Yes |
| Edit (Member) | Yes, but only from “Home” not from “Site Contents” or “Pages” | Yes | Yes | Yes |
| Read (Visitor) | No | No | No | Yes |
If we disable feature “Site Pages” – “Allows users to add new site pages to a site” on the root web – it does not affect subsites (subwebs).
Can we Activate/Deactivate the feature “Site Pages” using PowerShell?
(TBP)
References
– Microsoft “Allow users to create and comment modern pages“
See also:
– Allow commenting on modern pages
(Old) SharePoint Search: content-centric (SharePoint Search Center)
(New) Modern Search: people-centric (Teams, Office, OneDrive, Delve etc.)
Office graph = codename for collective set of services and insights we generate on top of the infrastructure that fast office graph group developed
= social Intel concepts (SharePoint home, Delve, OneDrive Discoverview) are derivatives of Office graph
Microsoft Graph = API ( +universal search API)
Turing technology – understands you, answers your question e.g. hover over doc -> doc summary (based on “deep speed” AI model)
announcement at Ignite23-pages blog
Modern Search: MS nailed the fundamentals, now start bringing it everywhere – to Teams first, then SharePoint (Nov 2020).
Modern Search Customizations – we’ll take the best from Classic SharePoint Search,
a lot will retire – investing in more flexibility
PnP modern Search
– custom result pages, webparts, branding theme; filters, refiners, scoping control )
– search layout designer – wysiwyg editor
pnp modern search – webparts (video)
https://microsoft-search.github.io/pnp-modern-search
Core idea behind Microsoft search is coherence
Bill Baer:
“People use search in a different ways
1) you have organisations who have a well-established intranet built around set of governance controls, a very clean architecture and they want to build a search into that intranet scenario; that’s why a lot of SharePoint capabilities are going to come along with Microsoft search for that particular endpoint
2) then you have other people who live their day in teams“
Shared search engine results page (developed once – transitioned everywhere)
Ctrl-F to search through teams (chats?) (contextual search)
Outlook search – more natural language
Image search (before eoy), +
teams chats, outlook groups conversations, yammer conversation -> bing, office.com, sharepoint
bookmarks (new promoted results)
Targeting bookmarks for the specific audience based on device/OS, region, security groups
SharePoint Search Admin Center -> will be migrated from SharePoint admin center to to Microsoft Search Admin Center transitioning (Search and Intelligence Admin Center) – long-running project custom dictionaries, spelling suggestions – will retire, (move to a graph-driven spellar)
promoted results -> bookmarks
Graph Connectors… Federation with Azure Cognitive Search
PowerBI search vertical
Standalone Search – AAD identity – Graph connector – Ingest your data – use Search = in Windows 10, Office.com ( e.g. for those who have their data in other productivity suite, have no intent to use m365, but want to search)
More info:
Current state of SharePoint Search and Microsoft Search scopes
Search is everywhere in Microsoft 365. You can search from SharePoint, Teams, Delve, Yammer etc.
But! From SharePoint you cannot search for Teams chats.
From Teams you cannot search for regular (no-group) sites.
Sites descriptions are totally out of search (including Yammer groups, Teams and regular sites).
So, what are the scopes of each search entry point in Office 365 and is there an entry point you can search for everything?
| Search scopes | SharePoint Search center | SharePoint home Office portal Office desktop app Delve | Teams | Bing |
| SharePoint content | Yes | Yes | Yes | |
| Teams content | Yes | Yes | Yes | Yes |
| Teams chats | Yes | Yes | ||
| Yammer content | Yes | Yes | Yes | |
| Yammer chat | Yes | |||
| User profiles | Yes | Yes | ||
Detailed:
| Scope | Out of Scope | |
| SharePoint Search Center | – all sites content (Teams, Yammer, regular), – user profiles – OneDrive | Teams chat Yammer chat |
| SharePoint Landing Page | same as SharePoint | same as SharePoint |
| Office.com | same as SharePoint | same as SharePoint |
| Delve | ||
| Teams | Teams content Teams chat | OneDrive Yammer User Profiles regular SharePoint sites |
| Bing | Everything* | * except people profiles content (e.g. about me) |
Seems like the only tool you can search for EVERYTHING with is Microsoft Bing:
More on Microsoft Search vs SharePoint Search and Microsoft Search RoadMap
Microsoft Office 365 Search: Find what you need with Microsoft Search in Bing