SP PnP PowerShell/Core 5-31

2:38 – Announcements

5:31 – PnP Provisioning Schema

  • https://github.com/SharePoint/PnP-Provisioning-Schema
  • Resolved most of the issues reported in the Schema repo
  • Added information about when items were added to the schema
  • Added ability to define site webhooks, not currently available in the engine because no SharePoint support
  • Client-Side Pages
  • Template Culture Info for the site we are provisioning
  • Scope attribute allows us to understand what kind of target we have for template, root site, sub web
  • Enable tree view for navigation for the site.
  • Role assignment ability to remove out of the box role assignment and add new role assignments, implemented in the schema but not in engine. Schema changes need to come before engine updates
  • Added Key column attribute for data import to prevent duplicate items being added as part of the provisioning
  • Update behavior to define how to handle existing items
  • Can define custom webhooks when list is created, webhooks last on the list for 6 months then need to be re-applied.
  • IRM Settings to define IRM rules
  • No Crawl attribute to define that the items will not be crawled by search
  • List experience to define choice of modern, classic experience, or let SharePoint decide
  • Default display/new/edit forms URL
  • Is application list to define if it is a application specific list
  • Ability to add property bag values to a folder
  • Flag to clear list of content types for document sets
  • List instance field refs can be added to add or remove fieldrefs from lists
  • Target file name option to define the name of the file instead of going with the default name of what it exists as in the template site
  • Image renditions support added
  • Site collections term group update behavior to allow overwrite existing term groups
  • Two releases in June to help implement the schema items into the engine
  • After June 2017 release all of the -spo commandlets will be removed

     

33:53 – Office365 Dev CDN

  • Public and Private CDN

  • E3+, CDN is included in your subscription
  • Public CDN Logical Flow

  • Anonymous access for public CDN is not your content, it is JS/images/CSS. Shouldn’t normally contain confidential information
  • Private CDN Assets are security controlled
  • Private CDN Logical Flow

  • CDN functionality disabled by default
  • Instructions to enable CDN

  • Demo
  • Public CDN is validated by referrer

 

58:11 – Q & A

  • Public CDN only available for your tenant

     

 

PnP Sites Core and PowerShell Special Interest Group May 3, 2017

Here is the summary for the PnP Sites Core and PowerShell SIG call from May 3, 2017. I will add the link to the video and add the timings when the video recording has been posted.

Updated May 6, 2017 – Added video link and timings.

 

3:16 – April Stats

  • 4,916 Unique Tenants
  • 2,048,306,419 http requests
  • 22,850 Unique Github Visitors (avg 2 weeks) – GitHub limitation
  • 127,343 Views in Github(avg 2 weeks)
  • Most used capability – Provisioning Engine 1306 tenants
  • Top 5 countries based on tenants
    • US
    • UK
    • Netherlands
    • Germany
    • Sweden
  • Top 5 countries based on requests
    • US
    • Netherlands
    • Denmark
    • Sweden
    • Germany
  • Guidance and code on customizations options around SPO modern experiences
  • They are aware of the limitations and missing functionality must make sure things are constant and not changing for next 3-5 years

8:28 – Modern UI Experience Scanner – Released

  • Demo by Bert Jansen
  • Analyzes your tenant for “modern” user interface compatibility
  • Scanning for:
    • Sites not using “modern” pages
    • Lists and Libraries rendering using the classic user interface and the reasons why they do so
    • Customizations in the modern user interface
  • Working on modern equivalent for user custom actions
  • Open source on Github – https://aka.ms/sppnp-modernuiscanner
  • Quick start guide on Github
  • Requires access to everything because it scans everything
    • Can use app-only Principal
      • Instructions on Github readme
      • Safe guard your client id and secret
  • Everything starts in parallel defaults to 10 threads
  • Can get throttled if you are too aggressive
  • Depending on site collection account it could take days to run, not a big deal because low memory usage
  • Outputs reports in csv files
  • Where should the modern page experience be enabled?
  • Enabled for all modern team sites
  • Enabled on most classic team sites
  • If the site has a lot of custom pages they assumed the site does not want modern experience
  • Modern ui not currently created for all list types
    • Announcements, tasks, and calendar lists
  • JSLink and XSLLink customizations disable modern experiences
  • Shows where the feature has been disabled site collection, web, or list
  • Publishing fields and geo-locations fields prevent modern ui
  • Reports show customizations which would be ignored on modern ui
    • Masterpage
    • Custom action
      • ScriptLink not allowed on modern ui
    • Alternate CSS

39:36 – New Provisioning Engine Schema design in Progress

41:12 – New Guidance

44:12 – Q&A

  • SharePoint FrameWork Referencing Styles – CSS/styles encapsulated with a prefix
  • Guidance on testing and provisioning a site – Provisioning engine tested on a regular basis
  • Dev/Test/Prod (ALM) – Working on Guidance