There are some new SharePoint Premium Content AI Microsoft Graph API endpoints. Allowing you through code to programmatically orchestrate document processing models. This allows scenarios such as provisioning a site and then applying a model to a library or processing a file/folder using a model to now be completed using Microsoft Graph.
This blog will show you how programmatically activate SharePoint document libraries for SharePoint Premium Image Tagging with PowerShell. This developer focused blog will provide the necessary PowerShell commands to add the special column Image Tags to a library with the property IsEnhancedImageTaggingEnabled set to TRUE. By doing so the library is then activated for Image Tagging. Uploaded images are then auto scanned with AI then tagged with descriptive keywords with no training or manual tagging required.
This blog will show how to add taxonomy columns to libraries and then turn them on for SharePoint Premium Taxonomy Tagging. This developer-focused blog will provide the necessary PowerShell commands to add a Taxonomy column to a library and update the field property ‘IsDocTagsEnabled’ to TRUE. By doing so, the column will be activated for Taxonomy Tagging, allowing documents to be automatically tagged when added to the library.
Over the past year Microsoft have released Sites.Selected permissions for both Microsoft Graph & SharePoint which can be given to an Azure AD App (App Registration). When created the app by default with Sites.Selected permissions does not have access to any SharePoint sites and has to be explicitly added added using Microsoft Graph or PnP PowerShell (Grant-PnPAzureADAppSitePermission) to the site(s) to be administered. Both processes only give the access Read or Write permissions to the site and not Full Control.
Today some people who are running targeted release on their M365 Tenant have been able to add the Board view to new and existing Microsoft/SharePoint Lists. I wanted to automate this creation of the Board View and following on from a previous blog post I did where I created a Modern Calendar on a list. I realised to add board view it followed the same pattern – using SharePoint Rest API. Through using the Edge Developer tools I figured out the JSON & Rest call required and that the view type was ViewType2: “KANBAN”
Today quietly Microsoft released a SharePoint Azure AD app registration permission level Sites.Selected. This allows PnP PowerShell cmdlets and CSOM to be used using SharePoint application permissions to a specific site(s). This is independent & different to the Microsoft Graph permission level Sites.Selected.
Recently we have finally been able to add a modern calendar view to a list in SharePoint Online through the UI. Before this a calendar view was only available in SharePoint classic mode. I wanted to automate this view creation and in order to do this I turned to my trusty friend PnP PowerShell. I figured it needed to be done using SharePoint REST API by creating a new SharePoint list view using ViewType2: "MODERNCALENDAR".