We are happy to announce the availability of new SharePoint Client-Side Object Model (CSOM) version targeted for the Office 365 or more specifically for SharePoint and Project Online. This release contains mainly some new APIs related to the GDPR requirements, which are also used by new SharePoint Online PowerShell cmdlets. 

You can find the latest CSOM package for SharePoint Online, including the Project Online CSOM assembly, from the NuGet gallery with an id of 'Microsoft.SharePointOnline.CSOM'. We are also working on updating the redistributable package at some point, but you can already right now start using some of these new capabilities in your solutions. We do recommend you to use the NuGet Package to gain access to the latest version, rather than downloading the SDK to your machine.

The version of the newly released CSOM package is 16.1.7618.1200. Previous versions of the NuGet have not been removed so that your existing solutions will continue working without issues and you can decide when the new version is taken into use. Notice that even though the NuGet version is increased to 16.1.7618.1200, actual assembly version of the released assemblies is 16.1.0.0. You can also check the version of the assemblies from the File Version attribute, which aligns with the NuGet version.

SharePoint Online Management Shell has been also updated to match with this CSOM release. You can find a new set of cmdlets listed in this article. 

Notice that since this NuGet package is targeted to SharePoint Online, you cannot use it directly in on-premises environments (SharePoint 2013 or 2016). This is because of the server side dependencies of the APIs. CSOM versioning model and dependency to your target environment are clarified in following blog post - Using correct Client-Side Object Model (CSOM) version for SharePoint customizations. We have released separate NuGet packages for on-premises. See following blog post for additional details - SharePoint CSOM versions for on-premises released as NuGet packages.

New properties and methods across assemblies

Here's a raw list of all the changes in the classes, properties and methods within this package. 

Microsoft.SharePoint.Client

Following properties, classes and methods have been added.

• public property Microsoft.SharePoint.Client.File.UniqueId
• public enum Microsoft.SharePoint.Client.RoleType
• public enum Microsoft.SharePoint.Client.SPVariantThemeType
• public class Microsoft.SharePoint.Client.TeamChannelManager
  
  
• public property Microsoft.SharePoint.Client.Web.HeaderEmphasis
• public property Microsoft.SharePoint.Client.View.ColumnWidth
• public enum Microsoft.SharePoint.Client.Sharing.Role
• public property Microsoft.SharePoint.Client.Utilities.WopiWebAppProperties.BootstrapperUrl
  
  

Microsoft.Online.SharePoint.Client.Tenant

Following properties, classes and methods have been added.

• public property Microsoft.Online.SharePoint.TenantAdministration.SiteProperties.DefaultLinkPermission
• public property Microsoft.Online.SharePoint.TenantAdministration.SiteProperties.DefaultSharingLinkType
  
  
• public property Microsoft.Online.SharePoint.TenantAdministration.SiteProperties.LimitedAccessFileType
• public method Microsoft.Online.SharePoint.TenantAdministration.Tenant.ConnectSiteToHubSiteById
• public method Microsoft.Online.SharePoint.TenantAdministration.Tenant.GrantHubSiteRightsById
  
  
• public property Microsoft.Online.SharePoint.TenantAdministration.Tenant.IsHubSitesMultiGeoFlightEnabled
• public property Microsoft.Online.SharePoint.TenantAdministration.Tenant.IsMultiGeo
  
  
• public property Microsoft.Online.SharePoint.TenantAdministration.Tenant.LimitedAccessFileType
• public method Microsoft.Online.SharePoint.TenantAdministration.Tenant.RevokeHubSiteRightsById
  
  
• public property Microsoft.Online.SharePoint.TenantAdministration.UserMigrationPropertiesEnumerableFilter.BatchId
• public property Microsoft.Online.SharePoint.TenantManagement.Office365Tenant.LimitedAccessFileType
• public enum Microsoft.Online.SharePoint.TenantManagement.SPOLimitedAccessFileType
  
  

Microsoft.SharePoint.Client.UserProfiles

Following properties, classes and methods have been added.

• public method Microsoft.SharePoint.Client.UserProfiles.PeopleManager.GetSPUserInformation
• public method Microsoft.SharePoint.Client.UserProfiles.PeopleManager.GetUserProfileProperties
  
  
• public method Microsoft.SharePoint.Client.UserProfiles.PeopleManager.HardDeleteUserProfile
• public method Microsoft.SharePoint.Client.UserProfiles.PeopleManager.RemoveSPUserInformation
  
  
• public method Microsoft.SharePoint.Client.UserProfiles.PersonalCache.DeleteCacheItemsAsync
• public method Microsoft.SharePoint.Client.UserProfiles.PersonalCache.ReadCacheOrCreateOrderById
  
  

New PowerShell cmdlets in SharePoint Online Management Shell release

Following cmdlets have been added to the latest release of SPO Managment Shell.  

• Export-SPOUserInfo
• Export-SPOUserProfile
• Remove-SPOUserInfo
• Remove-SPOUserProfile
  
  

“Sharing is caring”

SharePoint Team, Microsoft - 27th of April 2018

In this PnP Webcast, we concentrated on showing how to get access on the taxonomy information in SharePoint Online from SharePoint Framework without using classic JSOM, which does not work that well within the SharePoint Framework solution model. Showed technique with mimicking classic CSOM calls with REST can be considered as a workaround until native REST API support will be provided for taxonomy service. This model is not technically recommended, but still supported as it uses documented APIs.

Presentation covers following discussion points:

• How to access taxonomy client side? - using CSOM
• There's currently no REST APIs for taxonomy
• Understanding CSOM and using REST

Webcast demo shows following things:

• Demonstration of the taxonomy call from SharePoint Framework web part to retrieve terms
• Details on how the communication has been implemented in the web part code

Webcast presenters: Paolo Pialorsi, Vesa Juvonen

The presentation used in this webcast is available from new PnP SlideShare locations at https://www.slideshare.net/SharePointPnP.

Video on YouTube.

Additional resources

See following resources on the covered topics.

• SharePoint Framework documentation
• SharePoint Framework Tutorials
• SharePoint Client Query Protocol specification
  
  
• PnP Webcast - Debugging SharePoint Framework solutions
• PnP Webcast - Using Docker in SharePoint Framework development
• PnP Webcast - Calling enterprise applications securely from SharePoint Framework
• PnP Webcast - Using MSGraphClient within SharePoint Framework
• PnP Webcast – Upgrading Packages in SharePoint Framework Solutions
• PnP Webcast - SharePoint Framework Dialog Framework
• PnP Webcast - Reusable controls for your SharePoint Framework solutions
• PnP Webcast - Site collection app catalog
• PnP Webcast - Including assets in SharePoint Framework solution packages
• PnP Webcast - Migrating to SharePoint Framework Extensions
• PnP Webcast - ALM APIs for SharePoint Framework solutions and SharePoint add-ins (apps)
• PnP Webcast - Defining an icon for the client-side web part
• PnP Webcast - Working with Tenant Properties in SharePoint Online
• PnP Webcast - Deployment options for SharePoint Framework solutions
• PnP Webcast - SharePoint Framework in SharePoint 2016 Feature Pack 2
• PnP Webcast - VSTS Build and Release Pipelines for SharePoint Framework Solutions
• PnP Webcast - Common (mis)conceptions about SharePoint Framework
• PnP Webcast – Introduction to Visual Studio Extension for SharePoint Framework
• PnP Webcast - Calling external APIs securely from SharePoint Framework
• PnP Webcast - SharePoint Framework and organizational considerations
• PnP Webcast - Provisioning SharePoint assets for your SharePoint Framework solution
• PnP Webcast - Validating SharePoint Framework client-side web part property values
• PnP Webcast - Getting started with SharePoint Framework
  
  

What is SharePoint / Office Dev Patterns & Practices (PnP) webcast series?

SharePoint / Office Dev Patterns & Practices (PnP) webcast series covers different patterns, practices and topics around development with Office 365 and SharePoint. The majority of the topics are valid for the Office 365 and SharePoint on-premises. Our objective is to release a new webcast weekly or bi-weekly with few slides and a live demo of the covered topic. All webcasts are published at the PnP YouTube channel with additional references to the existing materials.

PnP is a community-driven open source project where Microsoft and external community members are sharing their learning's around implementation practices for Office 365 and SharePoint on-premises (SharePoint Framework and add-in model). Active development and contributions happen in our GitHub repositories under dev branch and each month there will be a master merge (monthly release) with more comprehensive testing and communications. Latest activities and future plans are covered in our monthly community calls which are open to anyone from the community. Download invite from http://aka.ms/SPPnP-Call. 

This is work done by the community for the community without any actual full-time people. It’s been great to find both internal and external people who are willing to assist and share their learning's for the benefit of others. This way we can build on the common knowledge of us all. Currently, the program is facilitated by Microsoft, but already at this point, we have multiple community members as part of the Core team and we are looking to extend the Core team with more community members.

If you have any questions, comments or feedback on SharePoint Development topics, PnP program or this blog post, please use the Microsoft Tech Community (SharePoint Developer group).

“Sharing is caring”

SharePoint Team, Microsoft - 30th of April 2018

Have you ever wondered how many users are launching your Office add-ins? Or how a recent change has impacted your user return rates?

Today we are excited to announce the availability of enhanced Office Add-In analytics within the Universal Store Dev. Center. The new Usage report shows how customers are using your add-in across Windows (2016), Mac (2016), iOS, and Web apps. Cohort return rates as well as breakouts by market are also included.

The new report can be accessed in both the Universal Store Dev. Center and your Seller Dashboard via the left navigation bar as “Usage” under the “Analyze” section.  Access to legacy reports are still available under “Legacy Reports.”

What is Seller Dashboard?

If you want your Office Add-in, Office 365 web app, Power BI custom visual or Microsoft Teams apps to appear in the Office Store, you need to submit it to the Seller Dashboard for approval.  Seller Dashboard also provides analytics on the performance of your solution.  You can visit our documentation on how to submit your solutions to the Office Store to learn more.    

Join us on the first Tuesday of every month for the Microsoft Graph API community call. You can download a recurring monthly calendar invite at https://aka.ms/microsoftgraphcall.

This month's topics included:

• Dan Kershaw from the Microsoft Graph team hosted the call and shared an overview about how to add your own custom properties to Microsoft Graph using Microsoft Graph extensions.
• Sarah Fender, from Cloud and Enterprises Security, discussed the brand-new Microsoft Graph Security APIs, and how you could use these in your applications, including some great demos featuring a sample app and partner-built app demos. Not to be missed!
• Nilesh Shah from the Office Platform team shared some cool demos of how to connect Excel and PowerBI to Microsoft Graph data. And he wasn’t done there.  Nilesh then introduced us to the Visual Studio connector service that makes it a breeze to configure your VS project to work with Microsoft Graph.
• Yina Arenas from the Microsoft Graph team rounded things off with some information about Build 2018– where to find the event planner and where Microsoft Graph will feature at Build.

Thanks to our community contributors: Giuliano De Luca, Waldek Mastykark, Nilesh Shah and John Liu.

Watch the call here.

View the presentation here. 

Next month’s call is on Tuesday, June 5, 2018. Submit your questions and topics here.

Resources:

From May's call

• Microsoft Graph extensions
• Microsoft Graph Security APIs
• Call Office 365 services in Visual Studio 2017 with the Microsoft Graph API
• Build 2018 live streaming

Microsoft Graph community call

• Recurring monthly community call calendar invite - https://aka.ms/microsoftgraphcall
• Monthly community call topic requests and questions - https://aka.ms/ybuw2i
• Previous monthly call recordings – Office Development YouTube Channel

Microsoft Graph feedback

• Microsoft Graph issues and technical questions - StackOverflow
• Microsoft Graph recommendations and suggestions - Microsoft Graph UserVoice

 SharePoint Dev Ecosystem / SharePoint Patterns and Practices (PnP) May 2018 update is out with a summary of the latest guidance, samples, and solutions from SharePoint engineering or from the community for the community. This article is a summary of all the different areas and topics around SharePoint Dev ecosystem during the past month.

What is SharePoint Patterns & Practices (PnP)?

SharePoint PnP is a nick-name for SharePoint Dev Ecosystem activities coordinated by SharePoint engineering. SharePoint PnP is community driven open source initiative where Microsoft and external community members are sharing their learning's around implementation practices for SharePoint and Office 365. Active development and contributions happen in GitHub by providing contributions to the samples, reusable components, and documentation.

PnP is owned and coordinated by SharePoint engineering, but this is work done by the community for the community. The initiative is currently facilitated by Microsoft, but already at this point, we have multiple community members as part of the PnP Core team and we are looking to extend the Core team with more community members.

Notice that since this is open source community initiative, there’s no SLAs for the support for the samples provided through GitHub. Obviously, all officially released components and libraries are under official support from Microsoft. You can use SharePoint Developer group in the Microsoft Tech Community for providing input and to ask any questions about the existing materials.

Some key statistics around SharePoint Dev topics from April 2018

• GitHub repository forks at most popular repositories in SharePoint GitHub organization 
  • SP Dev Docs - 346
  • SP Dev FX Web Parts - 586
  • SP Dev Fx Extensions - 111
  • PnP - 2803
  • PnP Sites Core - 473
  • PnP PowerShell - 451
• Unique visitors during past 2 weeks in SharePoint organization repositories - 38,306
• Merged pull requests across SharePoint repositories (cumulative) - 5,002
• Closed issues and enhancements ideas cross SharePoint repositories (cumulative) - 4,046
• SharePoint Online CSOM NuGet package downloads (cumulative) - 482,647
• PnP Core component NuGet package downloads (cumulative) - 197,074
• Page views in SharePoint Dev pages at docs.microsoft.com - 823,840
• Unique tenants using PnP components - 11,581
• Http requests towards SharePoint Online from PnP components (CSOM Core, PowerShell, PnP JS Core) - 9,986,170,484
• SharePoint Dev YouTube channel had 25,191 views with 154,577 minutes watch time

Main resources around SharePoint PnP and SharePoint development

• SharePoint development portal - https://developer.microsoft.com/en-us/sharepoint  
• SharePoint Dev Documentation - http://docs.microsoft.com/sharepoint/dev
• SharePoint Dev Community - http://aka.ms/sppnp - One location for all the resources and news around PnP
• PnP Community Discussions - http://aka.ms/SPDev-Community
• SharePoint Dev Videos on YouTube - http://aka.ms/SPDev-Videos
• Presentations at SlideShare
  
  

May 2018 monthly community call

Agenda for the Tuesday 8th of May 2018 SharePoint Dev Ecosystem / Patterns and Practices community call at 8 AM PST / 5 PM CEST:

• Monthly summary of SharePoint Development topics - Engineering updates from Build and community news - Vesa Juvonen (Microsoft) ~20 min
• New PnP provisioning schema improvements - Paolo Pialorsi (Piasys.com) ~10 min
• Latest capabilities in the PnP Provisioning Engine - Erwin van Hunen (Rencore) ~10 min
• Latest open-source SharePoint Framework controls for increasing productivity - Elio Struyf ~15 min
• Q&A ~5 min

Monthly community call will get recorded and release to PnP YouTube channel typically within 24 hours after the recording is ended. If you have any questions, comments or feedback, please participate in our discussions in the Microsoft Tech Community under SharePoint developer group. 

SharePoint Dev Blog posts

Here are the latest blog posts and announcements around SharePoint development topics from dev.office.com/blogs.

• 27th of April - New SharePoint CSOM version released for SharePoint Online - April 2018
• 11th of April - SharePoint Dev Ecosystem / Patterns and Practices - April 2018 monthly community call recording
• 3rd of April - Impact of Azure Access Control Retirement for SharePoint add-ins
  
  

PnP Webcasts

We started new PnP Webcasts are typically 15-30 min long conversational webcasts around a specific topic. This series was started in October 2015 and have continued releasing new videos since. All new webcasts are released on PnP YouTube Channel. Here are the new webcasts released after the last monthly release. We are looking into continuing the releases of the webcast in the future using weekly or bi-weekly schedule depending on the topics to be covered.

• 30th of April - Consuming taxonomy within SharePoint Framework solution
• 16th of April - SharePoint PnP Webcast – Debugging SharePoint Framework Solutions
• 3rd of April - Using Docker in SharePoint Framework development
  
  

General Dev, CSOM, PnP Core, PnP PowerShell SIG Bi-Weekly Call Special Interest Group (SIG)

General SP Dev, CSOM PnP Sites Core, PowerShell and Provisioning Special Interest Group (SIG) have bi-weekly meetings to cover the general SharePoint topics, CSOM and latest in the PnP CSOM core component, PnP PowerShell and in the PnP remote provisioning engine. These calls have also free Q&A section if you have any questions about SharePoint development in on-premises or in the cloud. Need to get a recommendation for your design or having a hard time with some APIs? - Drop by, ask a question and we'll help you.

You can download invite for the bi-weekly meeting from the following location. 

• Invite to bi-weekly call - https://aka.ms/sppnp-core-sig-call

All SIG meetings are being recorded and are available for view from PnP YouTube Channel. Here are the latest recordings of the SIG calls.

• 3rd of May - SP Dev news with engineering update. Modernizing SharePoint sites - open source tooling. Add-in submission process with AppSource.
• 19th of April - SP Dev news with engineering update. Site Design and Site Scripts, including create Site Design studio.
• 5th of April - SP Dev news with engineering update. The column formatting end-to-end story with UI and dev capabilities.

Interested in doing a community demo in these community calls? - Please let us know!

SharePoint Framework (SPFX) and JavaScript Special Interest Group (SIG)

SharePoint Framework and JavaScript Special Interest Group (SIG) has bi-weekly meetings to cover latest changes in the SharePoint Framework side, from the engineering perspective and to cover also latest development related to the PnP JS Core library. These calls are designed to have 50%/50% of content and demos and there has been already great community demos on the new SharePoint Framework Client-side web parts. If you're interested in showing your code, just let us know.

• Invite to bi-weekly call - https://aka.ms/sppnp-js-sig-call
• Gitter (Around the PnP JS Core) - https://gitter.im/OfficeDev/PnP-JS-Core

All SharePoint Framework and JS SIG meetings are recorded, so that you can check the demos and discussions if you can't make the actual call. You can find the latest recordings from the PnP YouTube Channel. Here are the latest recordings.

• 26th of April - SharePoint Framework engineering update, PnP JS Core update, Office 365 CLI update, SPFx controls update - Hub site extension selector sample. SPFx extensions and dynamic properties.
• 12th of April - SharePoint Framework engineering update, PnP JS Core update, Office 365 CLI update, SPFx controls update - Using the same codebase for both modern and classic custom footer. 

Interested in doing a community demo in these community calls? - Please let us know!

SharePoint Dev Ecosystem in GitHub

There are quite a few different GitHub repositories under the SharePoint brand since we wanted to ensure that you can easily find and reuse what's relevant to you. We do also combine multiple solutions to one repository so that you can more easily sync and get latest changes to our released guidance and samples. 

• sp-dev-docs - Source for new SharePoint dev center documentation exposed from http://dev.office.com/sharepoint
• sp-dev-fx-webparts - Client-side web part samples from community and engineering
• sp-dev-samples - Samples for add-ins, webhooks, and other API
• sp-dev-fx-extensions - Samples and tutorial code around SharePoint Framework Extensions
• sp-dev-fx-vs-extension - Open source Visual Studio IDE extension for creating SharePoint Framework solutions in the Visual Studio 2015 or 2017
• sp-dev-build-extensions - Different build extensions like gulp tasks and gulp plugins from the community and engineering around SharePoint development
  
• sp-dev-gdpr-activity-hub - Reference solution on the GDPR business case showing SPFx implementation with PowerBI and modern site customization
• sp-dev-solutions - Repository for more polished and fine-tuned reusable solutions build with SharePoint Framework
• sp-dev-fx-controls-react - Reusable content controls for SharePoint Framework solutions build with React
• sp-dev-fx-property-controls - Reusable property pane controls to be used in web parts
• sp-dev-column-formatting - New open-source community driven repository for column formatting JSON definitions
• sp-dev-site-scripts - New open-source community driven repository for community Site Designs and Site Scripts

• PnP - Main repository for SP add-in, Microsoft Graph etc. samples
• PnP-Guidance - Guidance, presentations, and articles which are partly synced to MSDN
• PnP-Sites-Core - Office Dev PnP Core component
• PnP-JS-Core - Office Dev PnP Core component for JavaScript
• PnP-PowerShell - Office Dev PnP PowerShell Cmdlets
• PnP-Tools - Tools and scripts targeted more for IT Pro's and for on-premises for SP2013 and SP2016
• PnP-Partner-Pack - Packaged guidance with detailed instructions on setting things up in Office 365 and in Azure.
• PnP-Transformation - Material specifically for the transformation process. Currently, includes samples around InfoPath replacement and transformation tooling from farm solutions to add-in model.
• PnP-Provisioning-Templates - Source for templates available from PnP Template Gallery at http://templates-gallery.sharepointpnp.com
• PnP-Provisioning-Schema - PnP Provisioning engine schema repository
• PnP-IdentityModel - Open source replacement of Microsoft.IdentityModel.Extensions.dll
  
  

What's supportability story around PnP material?

Following statements apply across all of the PnP samples and solutions, including samples, core component(s) and solutions, like PnP Partner Pack.

• PnP guidance and samples are created by Microsoft & by the Community
• PnP guidance and samples are maintained by Microsoft & community
• PnP uses supported and recommended techniques
• PnP implementations are reviewed and approved by Microsoft engineering
• PnP is open source initiative by the community – people who work on the initiative for the benefit of others, have their normal day job as well
• PnP is NOT a product and therefore it’s not supported by Premier Support or other official support channels
• PnP is supported in similar ways as other open source projects done by Microsoft with support from the community by the community
• There are numerous partners that utilize PnP within their solutions for customers. Support for this is provided by the Partner. When PnP material is used in deployments, we recommend being clear with your customer/deployment owner on the support model
  
  

Latest changes

SharePoint Framework samples 

These are samples which are available from the SharePoint client-side web part sample repository at https://github.com/SharePoint/sp-dev-fx-webparts or from the SharePoint Framework Extensions repository at https://github.com/SharePoint/sp-dev-fx-extensions.  

• Updates to SiteDesignStudio solution, which provides a web part to create Site Designs and Site Scripts for your tenant
• Updates to ColumnFormatter solution, which provides a web part to design column formatting definitions
• Updates for LinksAndHandlebarsTemplate solution, which shows how to use Handlebars as templating engine for client-side web part
  
  
• New sample react-graph-evalurl which shows Url validation for SharePoint using Office Graph
• New sample react-sitepages-metadata demonstrates how to extend SitePages library to enable updating existing items with metadata, and a roll-up includes a web part to display them.
• Multiple web parts updated to use latest SharePoint 1.4.1 version and cleaning existing SharePoint Framework client-side web part samples
  
  
• New react-application-sites-hubsite-switcher application customizer showing sites that are part of a Hub Site and renders a drop down to jump directly into a site. The customizer only renders if the site is a Hub site.
• Multiple extensions updated to use latest SharePoint Framework 1.4 version and cleaning in existing SharePoint Framework extension samples
  
  

Reusable open source controls for SharePoint Framework

New reusable controls initiative was announced in Ignite 2017 during September. There are two npm packages and source code repositories for the reusable controls which you can use in your SharePoint Framework solutions. We do welcome community contributions to these initiatives as well. There are two different repositories: sp-dev-fx-property-controls and sp-dev-fx-controls-react. Here are the changes on these repositories.

Added

• PropertyFieldCollectionData was added 58
• PropertyFieldOrder was added 19
• PropertyFieldSwatchColorPicker was added 55

• TaxonomyPicker control got added #22 #63 #64
• ListPicker control got added #34

Enhancements

• Allow the term set to be selectable in the PropertyFieldTermPicker #60

Fixes

• Fix for PropertyFieldColorPicker Palette Icon alignment issue in IE11 56
• Issue fixed when the optional selection property was not provided to the ListView #65
  
  

Community column formatting definitions

SharePoint Columns Formatting capability was released for First Release customers during October 2017. As part of the availability, we also announced the availability of open source repository for sharing different column formatting definitions. Following lists the changes in the column formatting area.

• No new column formatting samples during April, but adjustments and improvements on existing ones.
  
  

Community Site Designs and Site Scripts

SharePoint Site Designs and Site Scripts has been released for production usage during March 2018. As part of the availability, we also announced the availability of open source repository for sharing different Site Designs and Site Scripts. Following lists the changes in the Site Design and Site Script area.

• No new Site Designs or Site Scripts during April, but adjustments and improvements on existing ones.
  
  

Office 365 CLI 

Office 365 CLI was released in November 2017. This is an open source tool which enables you to controls tenant level properties in SharePoint Online or in Office 365. This is an alternative options for setting management on top of existing PowerShell cmdlets.

v1.2.0 release available with following changes

Added

• spo file remove - removes the specified file #287
• spohubsite data get - gets hub site data for the specified site #394
• spohubsite theme sync - applies any theme updates from the parent hub site #401
• spolistitem add - creates a list item in the specified list #270
• spolistitem remove - removes the specified list item #272
• spo page control get - gets information about the specific control on a modern page #414
• spo page control list - lists controls on the specific modern page #413
• spo page get - gets information about the specific modern page #360
• spopropertybag set - sets the value of the specified property in the property bag #393
• spo web clientsidewebpart list - lists available client-side web parts #367

• graph user get - gets information about the specified user #326
• graph user list - lists users matching specified criteria #327

Changes

• added support for authenticating using credentials solving #388
  
  

PnP CSOM Core and Provisioning Engine

PnP CSOM Core component is a wrapper on top of native SharePoint CSOM and REST API, which simplifies complex scenarios with remote APIs, one of the example is the PnP Provisioning Engine for remote templates. The first version of the PnP remote provisioning engine was released with the May 2015 release (3 years from this release). This list contains the main updates in this release:

Added

• Added WebApiPermissions support to provisioning engine.
• Added support to auto populate the BannerImageUrl and Description fields during save of a client-side page based on the found web parts and text parts on the page
• Added support for client-side page header configuration (no header, header with image, default header)
• Added ClientSidePage Title support in the provisioning engine.
• Added CommentsOnSitePagesDisabled property on web settings element in the provisioning engine.
• Added support for StorageEntities to the Tenant element in the Provisioning Engine. The user applying the template needs appropriate access rights to the tenant scoped App Catalog.
• Added SiteScripts and SiteDesigns elements to the Tenant element in the Provisioning Engine. The user applying the template needs to be tenant administrator.
• Added HubSiteUrl to the WebSettings element for the Provisioning Engine. The user applying the template needs to be tenant administrator.
• Added {SiteScriptId:[script title]} and {SiteDesignId:[design title]} tokens to the provisioning engine. This will only work if the user applying the template is tenant administrator.
• Added {StorageEntityValue:[key]} token to retrieve values from tenant level or (when applicable) site collection level. If a key is present at site collection level this value will take preference over the one from tenant level, following the behavior of the CSOM APIs.
• Added support for loading the classification of a unified group.
• Added GetPrincipalUniqueRoleAssignments web extension method. Get all unique role assignments for a user or a group in a web object and all its descendants down to document or list item level.
• Added support for SystemUpdate of taxonomy fields on list extension and item extension methods.
• Added support for using the ClientWebPart client-side web part to host "classic" SharePoint Add-ins on client side pages
• Added support for new schema v.2018-05
• Added support for Web API Permission in schema v.2018-05
• Added support for new schema v.2018-05 ==> 2018-05 is the new default schema
• Added async extension methods for feature handling and property retrieval
• Added extension methods to better support property handling on lists
• Added support for the implementation of the provisioning of dependent lookups fields 

Changed

• Fixed typo in TimeZone enum, and obsoleted incorrect value 
• Webhook server notification url in the provisioning engine now supports tokens 
• Fixed the setting of the page layout 
• Improved detection and configuration of the specific client-side web part data version
• Allow webhooks expiration to be updated without specifying the original webhook notification url 
• Fixed detecting of "The object specified does not belong to a list" error in the SetFileProperties extension method 
• Using ResourcePath.FromDecodedUrl to handle reading files and folders with special characters
• Fix async handling calling ClientSidePage.AvailableClientSideComponents
  
  

See also https://testautomation.sharepointpnp.com for day-to-day results and executed tests.

PnP JavaScript Core Library - PnPJs

Latest update is version 1.0.5 on the PnPJs library, which will be out soon after this blog post was released. Here's are the latest changes since the previous monthly release. 

Added

• @pnp/sp: Added web's getParentWeb helper method [PR]
• @pnp/sp: Added support for likes and comments on list items and modern pages [PR]

Fixed / Changed

• @pnp/nodejs: Fixed incorrect import for Request shims due to version change [PR]
• @pnp/sp: Fixed docs for web example code [PR]
• @pnp/config-store: Fixed docs and a bug in loading configuration [PR]
• @pnp/sp: Fixed clientPeoplePickerSearchUser and clientPeoplePickerResolveUser methods running error with verbose OData mode [PR]
• tooling: Fixed bug in gulp task test when using the --p flag .inactive.js test files were run [PR]
• docs: Fixed import references (@tarjeieo) [PR]
• @pnp/odata: Updated all parsers to use same error handling code path [PR]

• @pnp/odata: Removed core.ts and moved code into parsers.ts to simplify [PR]
  
  

This is a similar effort as what PnP initiative previously has done with the PnP CSOM Core Component together with the community. 

PnP PowerShell

PnP PowerShell providers more than three hundred additional PowerShell cmdlets, which can be used to manipulate content in SharePoint Online and in on-premises (SP2013, SP2016). These cmdlets are additive for SharePoint Online management shell, which concentrate more on the administrative tasks with SharePoint Online. 

Here are the latest changes in the PnP PowerShell

Added

• Added Enable-PnPPowerShellTelemetry, Disable-PnPPowerShellTelemetry, Get-PnPPowershellTelemetryEnabled
• Added Enable-PnPTenantServicePrincipal
• Added Disable-PnPTenantServicePrincipal
• Added Get-PnPTenantServicePrincipal
• Added Get-PnPTenantServicePermissionRequests
• Added Get-PnPTenantServicePermissionGrants
• Added Approve-PnPTenantServicePrincipalPermissionRequest
• Added Deny-PnPTenantServicePrincipalPermissionRequest
• Added Revoke-PnPTenantServicePrincipalPermission
• Added -Scope parameter to Get-PnPStorageEntity, Set-PnPStorageEntity and Remove-PnPStorageEntity to allow for handling storage entity on site collection scope. This only works on site collections which have a site collection app catalog available.
• Added -CertificatePassword option to New-PnPAzureCertificate
• Added output of thumbprint for New-PnPAzureCertificate and Get-PnPAzureCertificat

Changed

• Added -NoTelemetry switch to Connect-PnPOnline
• Updated Connect-PnPOnline to allow for -LoginProviderName when using -UseAdfs to authenticate
• Fixed issue where Add-PnPApp would fail where -Publish parameter was specified and -Scope was set to Site
• Fixed issue where New-PnPUnifiedGroup prompted for creation even though mail alias did not exist

Other

• Updated automatically generated PnP PowerShell cmdlet documentation at docs.microsoft.com
  
  

PnP sample library

Here are updates across the PnP code sample library by the community on the code and documentation, which is a great way to contribute as well.

• Updates to Provision.Modern.Cloud.Async which shows how to provision modern SharePoint sites in SharePoint Online using dynamically end user's access token for asycn processing
• Updates to Taxonomy picker to support synonym matching in search
  
  
• Updates toSharePoint.Modernization tool which can be used to batch updated classic pages to modern pages
• Updates to Search query tool v2.8: Small fixes and improvements 
  
  

SharePoint Dev articles 

SharePoint Dev articles are surfaced currently in docs.microsoft.com/en-us/sharepoint/dev. ´Since the last release, we have now merged also SharePoint PnP Solution guidance to docs.microsoft.com platform, so you'll only have one location to follow all relevant SharePoint Dev documentation and guidance. You can provide contributions to these documents by submitting documentation improvements using GitHub tooling. All of the SharePoint Dev docs are stored and surfaced from the sp-dev-docs repository. 

Here are new/updated articles on the SharePoint Development. 

• Overview and CSOM guidance for connecting SharePoint sites to new Office 365 groups
• Use web parts with full-width column
• Use SharePoint Framework client-side web parts with the full-width column
  
• Updates to transformation your classic SharePoint sites article series
  • Modernize your classic SharePoint sites
  • Modernize the user interface
  • Maximize your use of the modern list and library user interface
  • Modernize the customizations
  • Connect to an Office 365 group
  • Modernize the site branding
    
• Numerous other adjustments and updates based on input from the community
  
  

PnP Guidance videos 

You can find all SharePoint Dev videos on our YouTube Channel at http://aka.ms/sppnp-videos. This location contains already a significant amount of detailed training material, demo videos, and community call recordings. 

• No specific guidance videos on top fo the community call demos during this month
  
  

Key contributors to the May 2018 update

Here’s the list of active contributors (in alphabetical order) since last release details in SharePoint Dev repositories or community channels. PnP is really about building tooling and knowledge together with the community for the community, so your contributions are highly valued across the Office 365 customers, partners and obviously also at Microsoft.

Thank you for your assistance and contributions on the behalf of the community. You are making a difference!

• Alex Terentiev (SharePointalist) - @alexaterentiev
• Andrew Connell (Voitanos) - @andrewconnell
• Andrew Koltyakov (ARVO Systems) - @andrewkoltyakov
• andrewpat24 alias - andrewpat24
• Anthony Conrad - parithon
• Balamurugan Kailasam - kshsbala 
• Bartosz - Szab
• Chris Kent (DMI) - @theChrisKent
• Colin Dekker (D-Cubed) - colindekker
• Daniel Laskewitz (Sogeti) - @laskewitz 
• David Opdendries - @SharePointDavid
• Dennis Goedegebuure (Winvision) - expiscornovus
• Elio Struyf - @eliostruyf 
• Erwin van Hunen (Rencore) - @erwinvanhunen 
• Eric Shupps - @eshupps
• Franck Cornu (aequos) - @FranckCornu
• Francesco Zoccarato - fzoccara
• Gautam Sheth (Rapid Circle) - gautamdsheth
• Hugo Bernier - hugoabernier
• Jeff Burt (Credera) - TheJeffer
• Joel Rodrigues (CPS) - joelfmrodrigues
• Kev Maitland - kevmaitland
• Kaarlo Räihä - mcraiha
• krzysztofziemacki alias - krzysztofziemacki
• Luis Mañez (ClearPeople) - @luismanez
• Martin Dubec (Merck & Co) - cebud
• Martin Loitzl - mloitzl
• Mark Powney - mpowney
• Markus Möller (Avanade) - mmsharepoint
• Matti Paukkonen - mpaukkon
• Mikael Svenson (Puzzlepart) - @mikaelsvenson
• mptolly alias - mptolly
• Oleg Rumiancev - olegrumiancev
• Oliver Zeiser (MondayCoffee) - oliverzeiser
• Paolo Pialorsi (PiaSys.com) - @PaoloPia
• Paul Schaeflein - @paulschaeflein
• Radi Atanassov (OneBit Software) - @RadiAtanassov
• Richard Diphoorn - rdtechie
• Robert Jaakke (Mavention) - rjaakke
• Rodrigo Romano - RARomano
• Spencer Harbar - @harbars
• Stefan Bauer (n8d) - @StfBauer
• Steve Beaugé (Solutions pour SharePoint) - stevebeauge
• Tarjei E. Ormestøyl (Puzzlepart) - tarjeieo
• Teodora Ivanova (ClearPeople) - TeodoraI
• Tomi Tavela (Valo Intranet) - @tavikukko
• trevis62 alias - trevis62
• Tse Kit Yam - tsekityam
• Velin Georgiev - @velingeorgiev
• Vipul Kelkar (Rapid Circle) - vipulkelkar
• Vincent Biret (2toLead) - @baywet
• Waldek Mastykarz (Rencore) - @waldekm
  
• Yannick Plenevaux - @yp_code
  
  

Companies: Here's the companies, which provided support for PnP initiative for this month by allowing their employees working for the benefit of others in the PnP initiative. There were also people who contributed from other companies during last month, but we did not get their logos and approval to show them in time for these communications. If you still want your logo for this month's release, please let us know and share the logo with us. Thx.

 

 

 

 

 

 

 

We’re blogging the latest, greatest news from Build 2018 for the Office 365 developer community.  So, whether you’ve come to Seattle to attend in person, or are attending virtually from your home or office, you can stay on top of the live-stream or recorded keynotes, sessions, stories and trends that emerge from the big event.

Blog Posts and Information

• Microsoft Teams Developer Platform Enhancements Announced for Build 2018
• Harness the growing network of apps and insights in Microsoft Graph
• Conversations become actions in Outlook
• Azure Machine Learning, JavaScript Custom Functions, and Power BI Custom Visuals Further Expand Developers Capabilities with Excel

Check with us daily and/or follow us @OfficeDev on Twitter and we’ll make sure you don’t miss a thing.

At Build 2018, we’ve announced several technologies to help developers enrich emails with new interactive capabilities.  These capabilities allow developersto engage with their users more deeply in right in context within the email, thereby reducing the friction between intent and action. If your applicationsends notifications,  uses approvals in business processes, or connects to mail, calendar, and contact data, you can take advantage of new engagement opportunities across Outlook.  

Adaptive Cards provide new ways to create engaging conversations 

Many email conversations require and imply actions - such as approving an expense report or assigning a task to a team member.  With Actionable Messages,announced last year, developers can transform  their email notifications, workflows processes, and conversations into actions, enabling users to complete tasks faster right within Outlook. At Build 2018, we’re dramatically enhancing the capability of Actionable Messages in several ways, starting with the use of the Adaptive Cards as well as support for payments in Outlook. 

Adaptive Cards provide a rich display format along with actions inside of email messages

Adaptive Cardis a new card design format that issupported across Outlook, Windows in the Timeline View, Teams and within Cortana.  Every business process – and any service that sends a notification – can immediately benefit by adding adaptive cards directly into emails, bots, and Team chats.  Adaptive Cards are now supported for Actionable Messages within web-based Outlook clients, and will soon be supported in Outlook 2016 for Windows.  

You can now design your Actionable Message card using the Adaptive Card format. It’s as simple as adding JSON markup to the body of your emails and making HTTPS endpoints available to handle actions. Office 365 and Outlook take care of the rest, including beautifully rendering your card, allowing only authorized senders, and letting you ensure that actions are taken by expected users. 

Partners like GitHub, Asana, and Limeade will now support Outlook Actionable Messages withAdaptive cards to grow user engagement with their applications by lowering the friction of getting things done.  

It is very easy to build Actionable Messages using Adaptive Cards. Head over to our Actionable Message documentation, now featuring Adaptive Cards.  To create and design your own Adaptive Card, head over to the card playground and send the card to yourself using your Office 365 account and view it in Outlook on the web.   

Streamlining Payment Processes in Outlook

Payments in Outlook will enable users to pay bills and invoices directly from their inbox

Many emails in your inbox revolve around completing payment transactions such as paying abill or invoice. We will soon be introducing payments in Outlook to help users to pay bills or invoices, right in email, without needing to switch to another app or service.  Powered by Microsoft Pay, payments in Outlook is a fast and secure way to pay from within email. To start, it will be supported by a number ofpayment processors including Stripe and Braintree, billing services including Zuora, and invoicing services includingFreshBooks, Intuit, Invoice2Go, Sage, Wave, and Xero. 

Businesses that send bills or invoice notifications to customers over email can now embed a payment action within Outlook.  To get started working with payments in Outlook, please review our documentation. Note that Outlook is not a bill payment service and Microsoft is not acting as a bill pay agent. 

Payments in Outlook will roll out in phases, initially to a limited number of Outlook.com customers over the next few weeks and will be available more broadly in the coming months. 

Start engaging your users in Outlook with Adaptive Cards  

Adaptive cards extend Actionable Messages to make engaging customers wherever they work easier, and more streamlined.  Even processes like payments can now be resolved in the flow of working through email. This keeps customers focused, while also reducing task approval and completion times.  With an ability to embed Adaptive Card markup into existing mail processes, getting started with is easy. Review our overview documentation around adaptive cards to get started – we look forward to seeing Adaptive Cards arriving in users’ inboxes soon! 

We are excited to join the Office 365 team at Build 2018 to talk about what's new in the Microsoft Teams developer platform. Last year at Build, we announced our apps platform, unifying tabs, bots, Office 365 Connectors; new capabilities such as messaging extensions; our built-in app store; and our first APIs for Microsoft Graph. Today, we're building on that foundation by announcing several new features that will be available in Developer Preview and/or released over the next few months:

• An app store for your enterprise line-of-business (LOB) apps
• Microsoft Teams apps listed in AppSource
• Support for Adaptive Cards
• Microsoft Graph APIs for automating the provisioning and lifecycle of teams
• Microsoft Graph APIs for reading messages in channels
• Enhancements to Microsoft Teams App Studio to streamline the development process
• Support for apps in group chats
• Bots sending and receiving documents in 1:1 chat

Let's look at each of these in more detail.

Teams App Store

In January of this year, we released the Teams apps Store, a great way to find and install Microsoft Teams apps submitted to AppSource. However, not every Microsoft Teams app belongs in AppSource: in particular, Teams apps built to integrate with line-of-business (LOB) apps in your enterprise. The new Microsoft Teams LOB app store feature will allow an Office 365 tenant administrator to upload apps to a custom app catalog and distribute them within the organization. For example, consider a hospital with an app for managing hospital staff shift changes: a Teams app with these features can be loaded into the hospital's app catalog, allowing hospital staff to access the shift-change application within Teams. Teams apps can be uploaded via PowerShell cmdlets, Microsoft Graph APIs, and even using the Teams client itself:

In other AppSource news, as of today Microsoft Teams apps are listed in, and installable from, AppSource, in addition to the Store inside Teams. Many are listed today, and the rest will appear over the next few weeks.

Adaptive Cards

Last year at Build, Microsoft unveiled an early preview of Adaptive Cards, a cross-platform, open-source framework for exchanging rich, interactive cards. At Build 2018, we'll show Adaptive Cards in Microsoft Teams:

Support for Adaptive Cards is coming soon to Developer Preview, integrated with bots, custom Connectors, and messaging extensions. Adaptive Cards will soon appear across many other Microsoft products, including Outlook, Windows, and Cortana.

Microsoft Graph

The platform team has been hard at work extending our support for Teams APIs in Microsoft Graph. By this summer, we'll be releasing the current Teams Graph APIs from preview  to general availability, including: create and deleting teams, adding members and owners, adding and removing channels, change team settings. New APIs for cloning a team (including its apps and tabs) and managing enterprise LOB apps via Graph will also be available on graph.microsoft.com/beta soon. Taken together, the first wave of Teams Graph APIs are ideal for automated provisioning of teams/users/channels and managing the lifecycle of these teams on an ongoing basis: one of the top requests from developers, partners, and customers.

Another very common developer wish is APIs for reading the contents of messages in a channel, including threaded messages. We're granting that wish with the Teams Messaging APIs for Microsoft Graph, which will also be available on graph.microsoft.com/beta soon.

App Studio for Microsoft Teams

At the end of January, we debuted the preview version of the App Studio for Microsoft Teams, a tool that streamlines and automates the development process for creating Microsoft Teams apps, as well as making it easier to create great-looking apps matching the Teams design language. Today, we're announcing two new features:

• App packages in the cloud. The current version of App Studio stores its app packages locally, specific to a machine and to a specific client: if you use a different machine or move between the desktop and browser versions of Teams, you see different app packages. As of today, app packages will be stored in the cloud, associated with your Office 365 account, so you'll see the same thing no matter where you use App Studio (that is, like everything else in Teams).
• Inline bot registration. No more switching back and forth from the Bot Framework bot registration portal and remembering to activate the Microsoft Teams channel! This was one of the most error-prone steps in the Teams app development process, and it happened at the worst possible time: when a developer was first getting started. Soon, you can register your bot directly within App Studio, as well as update its messaging endpoint, something that bot developers do on a daily basis during the development process.

Apps in Group Chats

In Microsoft Teams today, users can interact with apps in a channel or individually. Except for a few limited cases, you can't add tabs to a group chat, and you can't use bots or messaging extensions in group chats. Soon, this will the ability to use apps in group chats will be available in Developer Preview, and you'll be able to use Teams apps everywhere.

1:1 Bots Sending and Receiving Documents

While bots can currently send images to users, it's never been possible to upload a text file, PDF, or Office document to a bot or for a bot to send documents to you. Working with the OneDrive team, we've defined a way to do this in a way that upholds the security and compliance standards you expect from Office 365. Soon, the ability for bots to send and receive files in 1:1 chat will be enabled in Developer Preview, enabling developers to create smarter bots to save you time and effort:

Summary

At Build today and throughout the week, you'll learn more about these enhancements to the Microsoft Teams developer platform…and more, including features that are a little further out. In particular, we are excited to announce the first step on the journey towards apps tailored for your enterprise with the Microsoft Teams LOB app store. We invite you to check out the Build 2018 videos on Channel 9, including the sessions we pre-recorded over the past few weeks.

Introduction

Microsoft Graph is the unified API endpoint that offers developers a gateway to the rich data and powerful insights behind a large and growing set of Microsoft products. Based on consistent REST-based standards, tools, and features, the set of scenarios you can power with the Microsoft Graph grows exponentially as new products, datasets and capabilities are added to the endpoint.

New datasets

The power of the Microsoft Graph is enhanced by the ease with which developers can traverse datasets from across the spectrum of Microsoft products to create experiences that are rich, relevant and insightful. As the amount of accessible data grows, so does the potential power of the Microsoft Graph. Here’s what’s new then, for Build 2018.

Security

It’s essential that organizations have powerful tools to combat cyberthreats. It's ideal when those tools are further enhanced with rich organizational context.  To this end, Microsoft is now previewing the Security API in Microsoft Graph, which eliminates the need for developers to individually integrate multiple security products. The Security API connects to the Microsoft Intelligent Security Graph to power real-time protection for Microsoft and third-party products and services. With this API developers can unify and standardize alert management and stream alerts to SIEM solutions like Splunk and IBM’s QRadar via Azure Monitor. In addition, they can receive aggregated responses from Federated security providers and drive threat analysis and response.

Activities and devices

Microsoft believes developers create human-centric scenarios that move with the user and blur the lines between their devices, regardless of form factor or platform. To do this there are two key components, both exposed thru Graph-accessible APIs: the Activity Feed API and the Device Relay API.  Activities make users more productive by helping them resume important tasks in your app quickly across devices. The device relay API enables your app to register itself, and discover, command, and message your app on the user's devices. By doing this, you can make the tasks your customers stay productive at work.  The Activity Feed APIs are now generally available, and the Device Relay APIs will follow soon. Developers can also get the client SDKs for Andriod and iOS here.

Access & authentication

Every organization must understand and manage how users access its data, and once access is granted, what restrictions they may place on that access.  We’re making several datasets available that help developers manage authentication and access within their organizations.  The Azure Active Directory team is making the Deleted User/Group Restore APIs and Office 365 Group Lifecycle Policy Controls generally available.  Additionally, APIs for accessing AD Terms of Use and Azure AD Audit Logs are available for Preview.

For developers building web-based add-in solutions for Office 365 canvases like Word, Excel, PowerPoint or Outlook, we’re offering a preview version of integrated SSO (Single Sign-On) to make user authentication and access to the Microsoft Graph APIs easy.

It’s going to be a big summer for Microsoft Teams APIs.  Developers can expect to see several new features added to the Microsoft Graph beta endpoint in the coming months.  By popular demand, we’re adding a new Teams Messaging API that allows you to read the contents of messages in a channel.  We’ll also offer new APIs for cloning teams and managing Enterprise LOB applications.  Stay tuned for more details!

In addition to new features appearing on the beta endpoint this summer, the Microsoft Teams folks will move the current set of Teams Graph APIs, which allow you to create and delete teams, add members and owners, and add or delete channels, from the beta endpoint into production.

The Microsoft Outlook team continues to move new datasets into production.  For Build this year there are several additions: developers can now create even richer Outlook integrations with expanded access to mailbox settings like Working Hours and Access to Shared Calendars, mailbox server settings including SupportedTimeZones and SupportedLanguages and message data including Message Rules, Message Categories, Flag Status and for network path details, InternetMessageHeader information.  We’ll also see a new Outlook Search Folders API added to the beta endpoint.

In other product news, developers working with OneDrive will find a few updates to those APIs, including support for additional formats in file conversion, and an update to the Permissions API.  We are also making a beta version of its File Preview API available.  We’ve put a lot of Intune resources into the Microsoft Graph this year, and most recently we’ve made additions for Android work profiles and VPN profiles, among a host of additional refinements to our device management resources.  If you develop solutions for Planner, the Planner beta API now includes the ability to query recent and favorite Plans.  We’ve released a beta version of APIs for Microsoft Bookings, our new online and mobile app that lets small businesses manage appointments.

New capabilities

Of course, as any organization changes and evolves, so does its data.  We continue to build out the capabilities developers need to detect and analyze changes so that they can create applications and services that react to the changing, dynamic nature of their customers’ businesses.

Delta queries, webhooks and batching

Delta queries are now available for the beta Planner API where developers can query for changes in tasks, plans and buckets.  Scoping filters, to filter by ID for Users and Groups are now in production, and SyncFromNow support for AAD allows the establishment of a “now” start-time value for querying changes against AAD datasets.  We’ve also made additional webhook updates, with webhooks for AAD Users and Groups moving into production, and the List Subscriptions API now generally available.  Finally, we’ve increased the JSON batching limit to 20 requests at a time, to help developers further optimize the performance of their applications.

OpenAPI

OpenAPI 3.0 (formerly Swagger) is a standards-based specification for describing web services to enhance interoperability.  There are hundreds of tools out there that already have support for OpenAPI.  We’re pleased to announce that this July, we will make the API description for Microsoft Graph publicly available for all Microsoft Graph versions. 

Managed access to Microsoft Graph data 

We are also making it easier to work with Office data in Azure, with a more direct capability to manage and direct access to Graph data for Insights applications. Now in private preview, access to Microsoft Graph data in Azure provides easier connections to Azure tools with the compliance and security benefits of applications managed end to end in Azure. 

SDKs

It’s possible to consume Microsoft Graph data in applications built in many languages.  To make the process easier for developers of different stripes, we maintain a variety of SDKs and code samples.  We’ve just released a generally available SDK for Java and have additional SDKs in developer preview.  We’re excited to see the response to these tools and to see what kind of applications they develop as a result.

Tools for citizen developers

Last but not least, the PowerApps and Microsoft Graph teams have jointly released a set of ten Microsoft Graph-powered PowerApps templates.  Users can leverage professional app designs, learn proper techniques and find inspiration to build their own Office 365-connected PowerApps built with Microsoft Graph.  We are excited to have people use these tools, and are taking actions based on the feedback we receive from users.

Conclusion

Whether you’re attending Build 2018 in person or online, thank you for taking the time to read our blog.  We hope that the Microsoft Graph datasets, capabilities and tools we’ve discussed here help you build more powerful, intelligent, and connected applications. 

We love to hear stories about how people are using Microsoft Graph, and your feedback is always appreciated.  You can join our community of passionate Graph developers a number of ways: join our Developer Program, attend our monthly Community Calls, Connect with us on Twitter by posting with #MicrosoftGraph, and send us your questions on Stack Overflow, tagged MicrosoftGraph.  Happy coding!

Today at Build, we announced a powerful set of capabilities to the Excel platform, offering developers, data scientists, and power users more opportunities to better work with data. Developers and data scientists can now to execute custom functions locally in JavaScript or with Microsoft Azure Machine Learning services to create their own powerful additions to Excel's catalog of formulas. Excel has enabled an out of the box bridge between business users and data science teams, to accelerate the digital transformation of businesses. With new support for Power BI Custom Visuals, developers will be able to build new kinds of data visualizations in Excel — giving users a much more diverse charting experience, right in Excel. Finally, Excel will integrate with Flow, allowing users sending data directly from a spreadsheet to a range of services. Read on to learn more.

Machine Learning and JavaScript custom functions for developers and data scientists.

Custom functions (similar to "user-defined functions" or "UDFs") are ways for developers to extend Excel's built-in set of formula functions. Users can create their own functions locally in JavaScript or with Machine Learning teams earning services. They can see and run these functions in Excel alongside built-in functions like =SUM or =VLOOKUP. The best part is that those same functions will work everywhere add-ins do: on PC, Mac, and iPad, and in Excel Online.

JavaScript custom functions

Office developers have been wanting to write JavaScript custom functions for many reasons, such as:

• Calculate math operations, like whether a number is prime.
• Bring information from the web, like a bank account balance.
• Stream live data, like a stock price.

Starting today, developers can build JavaScript custom functions at https://aka.ms/customfunctions. They're already enabled for Windows, Mac, and Excel Online.

Using a custom function in Excel

Machine Learning functions

Machine Learning functions can be created by AI developers, including data scientists and other experts. The functions are each based on a service that calculates or predicts values with a machine learning model. Once the model is deployed, the creators can enable it for anyone they choose. Within a company, administrators can configure who has access to which proprietary functions. Then, every time someone wants to run the function, they simply type in a cell, just like for any other Excel function. The function calls a live web service on the company’s Azure subscription and returns the result asynchronously.

There are many useful function types developers can enable with Machine Learning, such as:

• Smart forecasting, like predicting the future revenue trend at a company based on time series data in Excel.
• Classification problems for many Excel rows, like fraud detection from credit card transactions.
• Any custom Python code, like a function to analyze text in cells.

Power BI Custom Visuals for developers and power users.

Custom Visuals enable developers to extend the existing chart set in Excel and Power BI using standard Open Source technologies, like JavaScript and D3. If you’ve built a cool visualization based on web technologies, and you’re wondering how to reach the millions of Excel users that insert charts daily, this feature is for you. Or, if you’re a Power BI developer who has already built custom visuals, your visual can now reach a much wider audience. That’s because the same technology powers the Custom Visuals feature in both products. You can write your visual once, and have it work in both places. 

Here are some examples of Custom Visuals that exist today:

Examples from rich third-party ecosystem of Power BI Custom Visuals in Excel.

Custom Visuals provide several key benefits that make them an appealing choice for data visualization development in Excel including:

• Intuitive insertion experience: Custom Visuals live alongside existing charts in Excel. There are new entry points in the Chart ribbon, as well as a dedicated tab in the Insert Chart Insert dialog. The result is a familiar experience for users.
• Tailored Office Store experience: Like Office add-Ins, Custom Visuals can be published to the Microsoft Store. Exploring new charting options in the store is a one-click tailored experience that lets users navigate directly to a set of Custom Visuals.
• Intuitive UI controls: Excel provides common UI helping users connect visuals to their spreadsheet data, as well as configure properties. Providing this UI gives users consistent experience across all visuals. And having ready-made controls saves development time, allowing developers to stay focused on the visual content itself.
• Enterprise ready: Not all Custom Visuals are meant for the public Microsoft Store. Enterprise developers can continue building visuals in-house for their specific line-of-business needs (such as, for example, an airline company building a custom “airplane visual” for displaying information about seat booking). Office 365 admins will have the ability to deploy visuals in the same way that Office add-ins are deployed, and those new chart types will appear in the Insert Chart Insert dialog automatically without any additional work needed by users.

Customs Visuals live with other Excel charts. Visuals acquired from the store, or those deployed by an Office 365 administrator, will automatically appear here. The store for Custom Visuals can also be launched from here  Note, these visuals are just examples of the types of visuals in the Office App Store.

Excel provides a tailored view of the Office App Store that lets you focus on just the Custom Visuals. Note, the example visuals shown here are existing Custom Visuals for Power BI and may not all be available in Excel.

The task pane helps users connect their Custom Visuals to spreadsheet data, as well as configure settings on the visual.  The same task pane appears for all visuals, making the user experience easy and familiar for users across all visuals.

The combination of a more tightly integrated experience together with a customized store and a consistent UX, will give data visualization developers maximum reach to their audience. For more information, visit API documentation for Custom Visuals to get started today writing visuals for Power BI. Visit the Custom Visuals Store to see what kinds of visuals are currently offered.

Flow integration with Excel

With this integration, users can create, manage, and most importantly run automated workflows on Excel tabular data. Via Flow, users will be able to send data from their spreadsheets hosted in SharePoint and OneDrive for Business to a wide range of services such as Teams, Dynamics 365, Visual Studio Online, Twitter, etc. The integration will first be shipped as an add-in in the Office Store and will become an in-the-box component later this year.

These new capabilities are the result of continuous innovation to make Excel a more flexible and intuitive data analysis tool and expand developer opportunities. To stay connected to Excel and its community, read Excel blog posts, and send us ideas and suggestions for the next version of Excel through our UserVoice. You can also follow Excel on Facebook and Twitter.

Availability

JS custom functions for Excel is available now in Developer Preview to Office 365 subscribers enrolled in the Office Insiders program. Azure Machine Learning functions and Power BI Custom Visuals will be rolling out in preview soon—stay posted @OfficeDev

SharePoint monthly community call is our monthly event for SharePoint developers to stay up to date on the latest changes to SharePoint Dev topics from engineering and community perspective. This monthly community call is on every second Tuesday of each month where we go through a summary of SharePoint Development engineering news, latest guidance, status in UserVoice, community contributions and other relevant topics. 

You can also check the latest updates from the monthly summary at dev.office.com/blogs.
You can download a recurrent invite for these monthly calls from http://aka.ms/spdev-call.

This is the recording of SharePoint Dev Ecosystem / Patterns and Practices (PnP) monthly community call from Tuesday 10th of April 2018. Here's used agenda with direct links to specific sections, if you want to directly jump to a specific topic (will redirect your browser to SharePoint Dev YouTube Channel).

• Latest SharePoint community metrics from April 2018 (YouTube, GitHub etc.) -  4:29
• Top 10 UserVoice entries for SharePoint Dev and quick status - http://aka.ms/spdev-uservoice - 12:03
• Summary of May 2018 Release - Summary of released materials around SharePoint Development since last monthly call - 13:30
• Community contributors and companies which have been involved - 15:14
• A quick look at the updated SharePoint Development roadmap - 17:07
  
  
• Demo - SharePoint Framework solutions as Microsoft Teams tab - Vesa Juvonen - 21:22
• Demo - Latest changes in PnP Provisioning Schema - Paolo Pialorsi- 30:45
• Demo - Latest changes in PnP Provisioning Engine - Erwin van Hunen - 45:12
• Demo - Latest changes in the SharePoint Framework reusable controls - Elio Struyf - 55:18

Full recording - available from SharePoint Developer YouTube channel - http://aka.ms/spdev-videos.

Presentation slides used in the call

Additional resources

Additional resources on covered topics and discussions.

• SharePoint Development May 2018 monthly summary
• Recurrent invite to SharePoint Development monthly calls - http://aka.ms/spdev-call
• SharePoint Developer documentation - http://aka.ms/spdev-docs
• SharePoint Development Issues - http://aka.ms/spdev-issues
• SharePoint GitHub organization - http://github.com/SharePoint
• SharePoint Development UserVoice - new feature requests - http://aka.ms/spdev-uservoice
  
  

"Too many links, can't remember" - not a problem... just one is enough with http://aka.ms/sppnp.

“Sharing is caring”

SharePoint Team, Microsoft  - 10th of May 2018

At Microsoft Build, we previewed several upcoming changes and improvements coming to SharePoint Framework. You’ll see these changes start to release over the coming weeks, and we’ll go into more detail at the upcoming SharePoint Conference – North America. Watch Vesa Juvonen’s presentation from Build to see more detail around these new components.

SharePoint Framework 1.5 – New Flexibility for Retrieving Packages

SharePoint Framework (SPFx) 1.5 will focus on continuing to respond to feedback and incorporate stability fixes. Numerous issues – based on your feedback – have been addressed and are included.

We are also adding new choices for using different types of package managers within SPFx, to provide more flexibility in how you retrieve new packages. You can get packages via the yarn and pnpm package managers via this new flexibility.

New Releases with Experimental Components

Starting with SharePoint Framework version 1.5, you’ll be able to opt-in to new experimental packages, which extend the set of stable packages that SPFx releases will include.

These experimental packages deliver new features that are still under consideration and under development. For any new experimental component, we really value your feedback via SharePoint GitHub issues. Keep in mind, however - any experimental feature may never be released, or may undergo significant changes before it’s ready to use with your customers – so please don’t release any SharePoint Framework apps that use experimental features.

Global Deployment of SharePoint Framework Extensions

Today, SharePoint Framework Extensions require installing an app within individual site collections. This specificity is useful for departmental scenarios, where you want to have a very extensively customized portal and don’t want the customizations for that portal to become available in other sites.

Deploy standard footers across your tenancy, along with other types of extensions, with global deployment of SharePoint Framework extensions

We’ve also seen that a number of SharePoint Framework Extension scenarios work best when broadly applied across your SharePoint tenancy. For example, customers may want a consistent footer element with disclaimer or confidentiality text. Customers may also want to deploy list view command set extensions broadly across your tenancy to expose new tools.  To solve this, global deployment of SharePoint Framework extensions provides new options to broadly deploy items across your tenancy. 

Global Deployment of SharePoint Framework extensions will be offered as an experimental component in the coming weeks.

Dynamic Data

Web parts and extensions are designed to work on a page with other web parts. Frequently, these web parts and extensions can benefit from shared data and context – to support consistent preferences, share current user interface state, or at a minimum, avoid retrieving the same data that other components may have retrieved.

To support this, the SharePoint Framework will support a basic event subscription and publishing model. Different web parts and extensions can subscribe to custom-designed events. When data needs to be shared from a web part or extension, it can push the data through an event to any downstream subscribers.

Adding SharePoint Pages as a Tab in Teams

SharePoint Pages provide team leaders with the most flexible canvas and a robust collection of web parts. Over the coming weeks, you can add rich SharePoint Pages directly within Teams channels. This makes your custom designed SharePoint Framework components available in Microsoft Teams, bringing together all of the best tools in one place. Now, as you develop new extensions for Teams, consider using SharePoint pages and SharePoint Framework. 

In addition, we’re also working towards directly exposing SharePoint web parts, and their configuration options, directly as a Tab within Microsoft Teams.

Over the coming weeks, these improvements help you get your SharePoint customizations more broadly deployed – across tenancies, and within Microsoft Teams. New developer infrastructure provides new ways to connect parts, and use additional packaging frameworks. Taken together, SharePoint Framework continues to expand with new tools to make development and deployment easier, along with new places where you can share your work across teams.  Stay tuned for more updates coming from SharePoint Conference North America - we look forward to your feedback!

In this PnP Webcast, we concentrated on covering different methods to activate SharePoint Framework extensions in SharePoint sites. You can use tenant-wide deployment option to activate your SharePoint Framework client-side web parts in sites, as there is a web part picker for showing them, but there's no site level picker for extensions. This means that you will need to explicitly enable the extension in the site before it's being properly rendered. This webcast concentrates on covering the different options around this with live demos.

Notice. At the time of releasing this webcast, global deployment option is not available to be used. This capability was announced in Build 2018 and demonstrated in this webcast using an internal Microsoft test tenant.

Presentation covers following discussion points:

• Deployment options for SharePoint Framework solutions
• Activation options for SharePoint Framework extensions in sites - Local activation, on-demand activation and global activation

Webcast demo shows following things:

• Demonstration of the different options in practice
• Deployment of extension to the site by installing package explicitly to site
• Using tenant-scope deployment option in the solution and activating extension in the site using an API, Office 365 CLI or PnP PowerShell
• Using global deployment option to activate extension automatically in sites

Webcast presenters: Vesa Juvonen, Waldek Mastykarz

The presentation used in this webcast is available from new PnP SlideShare locations at https://www.slideshare.net/SharePointPnP.

Video on YouTube.

Additional resources

See following resources on the covered topics.

• Updates from Build: New improvements for SharePoint Framework coming soon - Blog post on SharePoint development announcements form Build 2018
• Leveraging SharePoint as a development platform for the modern intranet - SharePoint Framework session from Build 2018

• SharePoint Framework documentation
• Getting started tutorials for SharePoint Framework Extensions
  
  
• PnP Webcast - Consuming taxonomy within SharePoint Framework solution
• PnP Webcast - Debugging SharePoint Framework solutions
• PnP Webcast - Using Docker in SharePoint Framework development
• PnP Webcast - Calling enterprise applications securely from SharePoint Framework
• PnP Webcast - Using MSGraphClient within SharePoint Framework
• PnP Webcast – Upgrading Packages in SharePoint Framework Solutions
• PnP Webcast - SharePoint Framework Dialog Framework
• PnP Webcast - Reusable controls for your SharePoint Framework solutions
• PnP Webcast - Site collection app catalog
• PnP Webcast - Including assets in SharePoint Framework solution packages
• PnP Webcast - Migrating to SharePoint Framework Extensions
• PnP Webcast - ALM APIs for SharePoint Framework solutions and SharePoint add-ins (apps)
• PnP Webcast - Defining an icon for the client-side web part
• PnP Webcast - Working with Tenant Properties in SharePoint Online
• PnP Webcast - Deployment options for SharePoint Framework solutions
• PnP Webcast - SharePoint Framework in SharePoint 2016 Feature Pack 2
• PnP Webcast - VSTS Build and Release Pipelines for SharePoint Framework Solutions
• PnP Webcast - Common (mis)conceptions about SharePoint Framework
• PnP Webcast – Introduction to Visual Studio Extension for SharePoint Framework
• PnP Webcast - Calling external APIs securely from SharePoint Framework
• PnP Webcast - SharePoint Framework and organizational considerations
• PnP Webcast - Provisioning SharePoint assets for your SharePoint Framework solution
• PnP Webcast - Validating SharePoint Framework client-side web part property values
• PnP Webcast - Getting started with SharePoint Framework
  
  

What is SharePoint / Office Dev Patterns & Practices (PnP) webcast series?

SharePoint / Office Dev Patterns & Practices (PnP) webcast series covers different patterns, practices and topics around development with Office 365 and SharePoint. The majority of the topics are valid for the Office 365 and SharePoint on-premises. Our objective is to release a new webcast weekly or bi-weekly with few slides and a live demo of the covered topic. All webcasts are published at the PnP YouTube channel with additional references to the existing materials.

PnP is a community-driven open source project where Microsoft and external community members are sharing their learning's around implementation practices for Office 365 and SharePoint on-premises (SharePoint Framework and add-in model). Active development and contributions happen in our GitHub repositories under dev branch and each month there will be a master merge (monthly release) with more comprehensive testing and communications. Latest activities and future plans are covered in our monthly community calls which are open to anyone from the community. Download invite from http://aka.ms/SPPnP-Call. 

This is work done by the community for the community without any actual full-time people. It’s been great to find both internal and external people who are willing to assist and share their learning's for the benefit of others. This way we can build on the common knowledge of us all. Currently, the program is facilitated by Microsoft, but already at this point, we have multiple community members as part of the Core team and we are looking to extend the Core team with more community members.

If you have any questions, comments or feedback on SharePoint Development topics, PnP program or this blog post, please use the Microsoft Tech Community (SharePoint Developer group).

“Sharing is caring”

SharePoint Team, Microsoft - 14th of May 2018

The Microsoft Teams community call is our regular event for developers to stay in sync with Microsoft Teams. We’ll share updates, tips, and connect you to the product teams behind Microsoft Teams. In addition, we’ll have a technical deep dive on a specific topic: from tooling, to practical use cases, (e.g. Authentication, Teams App Studio) to highlighting how organizations leverage Microsoft Teams. At the end of each call, there’s an opportunity to ask us questions and share feedback. 

This month's topics included some highlights from Build 2018: 

• Enhancements to Microsoft Teams App Studio to streamline the development process 
• Demo - SharePoint pages as tabs  
• Demo - Support for adaptive cards  
• Demo - An app store for your enterprise line-of-business (LOB) apps  
• Sneak peek attask modules 

Watch the call here. 

View the presentation here.  

Next month’s call is on Tuesday, July 17, 2018 at 8:00AM PDT. Download the calendar invite at https://aka.ms/microsoftteamscommunitycall

Resources: 

From May's call 

• Microsoft Teams Graph APIs​ 
• Microsoft Teams Developer Platform Enhancements Announced for Build 2018 

Microsoft Teams resources and feedback 

• Yeoman generator to build Teams apps - https://github.com/OfficeDev/generator-teams  
• Microsoft Teams developer documentation - https://aka.ms/teamsdevdocs  
• Microsoft Teams issues and technical questions - StackOverflow 
• Microsoft Teams recommendations and suggestions - Microsoft Teams User Voice 

Additional resources 

• Office Developer repository - https://github.com/OfficeDev 
• Join the Microsoft Office 365 Developer Program- https://dev.office.com/devprogram 

We're pleased to announce that the Excel JavaScript 1.7 API is now generally available! We received lots of great feedback on the design of the APIs during the beta period and we appreciate your active participation. Our mission to provide a richer JavaScript library for Excel remains unchanged; you can look forward to new and enhanced APIs in the near future. Today we are excited to announce that more than four hundred new APIs  are now available for you to use to create and amaze your customers with more powerful Excel add-ins! 

What's new in in 1.7? 

• Events - Enrich your Excel add-in experiences with new coauth-proofed events. In 1.7 we added  onChanged, onSelectionChanged, onAdded, and onActivated/onDeactivated to many Excel objects. 
• Customize chart elements - We added new APIs for charts to enable richer visualizations. With these APIs, add-ins can change the appearance of a chart and add series, trendlines, axis, titles and more.   

• Custom and built-in document properties - Create, read, delete, and update  custom document properties, as well as built-in document properties. 
• Styles - Apply built-in styles or create and apply your own custom styles. 
• More worksheet capabilities - Copy worksheets, as well as other worksheet properties such as setting tab colors or the visibility of gridlines, within your workbook. 
• Password protection for workbooks. 

Office 365 users can get the benefit of these new APIs today! To use our new API, upgrade Excel to version 1801 (Build 9001.2171) or later. For iOS/Mac/Online minimum versions, see requirement sets page.  

Do you want to participate in the design of upcoming Excel JavaScript preview APIs? Excellent! Visit the Excel JavaScript API Open Specification. 

You can also try out the new API features by using the built-in code snippets that are available in Script Lab. In Script Lab, you'll find samples that use preview APIs listed in the Preview APIs category. 

We encourage you to try out the new APIs and tell us what you think. You can post questions about the APIs on Stack Overflow (tag with office-js), make suggestions for the docs on GitHub, or suggest new API features on UserVoice. 

We are happy to announce the availability of new SharePoint Client-Side Object Model (CSOM) version targeted for the Office 365 or more specifically for SharePoint and Project Online. This was mainly a small maintenance release with minimal updates on the CSOM API surface.

You can find the latest CSOM package for SharePoint Online, including the Project Online CSOM assembly, from the NuGet gallery with an id of 'Microsoft.SharePointOnline.CSOM'. We are also working on updating the redistributable package at some point, but you can already right now start using some of these new capabilities in your solutions. We do recommend you to use the NuGet Package to gain access to the latest version, rather than downloading the SDK to your machine.

The version of the newly released CSOM package is 16.1.7723.1200. Previous versions of the NuGet have not been removed so that your existing solutions will continue working without issues and you can decide when the new version is taken into use. Notice that even though the NuGet version is increased to 16.1.7723.1200, actual assembly version of the released assemblies is 16.1.0.0. You can also check the version of the assemblies from the File Version attribute, which aligns with the NuGet version.

SharePoint Online Management Shell has been also updated to match with this CSOM release. You can find a new set of cmdlets listed in this article. 

Notice that since this NuGet package is targeted to SharePoint Online, you cannot use it directly in on-premises environments (SharePoint 2013 or 2016). This is because of the server side dependencies of the APIs. CSOM versioning model and dependency to your target environment are clarified in following blog post - Using correct Client-Side Object Model (CSOM) version for SharePoint customizations. We have released separate NuGet packages for on-premises. See following blog post for additional details - SharePoint CSOM versions for on-premises released as NuGet packages.

New properties and methods across assemblies

Here's a raw list of all the changes in the classes, properties and methods within this package. 

Microsoft.SharePoint.Client

Following properties, classes and methods have been added.

• public property Microsoft.SharePoint.Client.CopyMigrationOptions.NameConflictBehavior
• public property Microsoft.SharePoint.Client.HubSiteCreationInformation.SiteDesignId
• public enum Microsoft.SharePoint.Client.MigrationNameConflictBehavior
  
  
• public property Microsoft.SharePoint.Client.SharingLinkInfo.BlocksDownload
• public property Microsoft.SharePoint.Client.SharingLinkInfo.IsDefault
  
  
• public method Microsoft.SharePoint.Client.TeamChannelManager.DemoteTeamChannelById
• public method Microsoft.SharePoint.Client.TeamChannelManager.DemoteTeamChannelByPath
• public method Microsoft.SharePoint.Client.TeamChannelManager.PromoteToTeamChannelById
• public method Microsoft.SharePoint.Client.TeamChannelManager.PromoteToTeamChannelByPath
  
  
• public property Microsoft.SharePoint.Client.Web.FooterEnabled
  
  

Microsoft.Online.SharePoint.Client.Tenant

Following properties, classes and methods have been added.

• public property Microsoft.Online.SharePoint.TenantAdministration.HubSiteProperties.SiteDesignId
• public property Microsoft.Online.SharePoint.TenantAdministration.SPOSitePropertiesEnumerableFilter.GroupIdDefined
  
  
• public property Microsoft.Online.SharePoint.TenantAdministration.Tenant.SyncPrivacyProfileProperties
• public property Microsoft.Online.SharePoint.TenantManagement.Office365Tenant.SyncPrivacyProfileProperties
  
  

“Sharing is caring”

SharePoint Team, Microsoft - 4th of June 2018 - Notice that May release was delayed for few days due technical challenges, which is why actual release happened on early June.

SharePoint Framework version 1.5 is now available, bringing both new tools to make your development more efficient as well as a new channel for trying new preview features.

Tailor development to your preferences with new package managers

SharePoint Framework version 1.5 contains new support for switching the underlying package manager in use, with optional support for PNPM and Yarn package managers in addition to the default npm package manager. These package managers contain different ways to internally retrieve and organize project packages, but importantly, should not change how you write code against SharePoint Framework projects. Yarn contains new module caching capabilities that speed install times as well as additional package integrity verification techniques. PNPM adds additional integrity verification capabilities as well as hard and symbolic links to avoid repetitively storing the same version of packages, which can save storage and speed project updates.

You can use these new package managers by specifying them in the commandline as you work with Yeoman.

Another new capability introduced in SharePoint Framework version 1.5 is the ability to customize new project experiences. With a customizable Yeoman generator, developers can extend the default new SharePoint Project experience to add additional options for development, including new project templates and framework integrations. Expect to see a more rich and robust, community-powered set of enhancements for kicking off new projects coming to a yo near you.

Finally, we’ve completed a round of new API updates documenting SharePoint Framework TypeScript APIs.

New channel for beta capabilities

Interested in getting a peek at new, upcoming SharePoint Framework capabilities? With SharePoint Framework 1.5, we are introducing a new channel for getting preview-level features you can work with. A specific yeoman label – plusbeta – creates projects that contain both version 1.5 release components as well as optional new beta components. We expect future SharePoint Framework releases to have similar "plusbeta" capabilities available at release. To create new projects using the latest beta components, you can generate them in yeoman with the following command line option:

yo @microsoft/sharepoint --plusbeta

It is important to note that these beta components will iterate and change across releases based on your feedback, and the final release date behind these preview features is not set. Many features will remain in the plusbeta package across many releases. As always, you should not deploy projects developed with beta components to production. For more details, read our documentation around the new plusbeta functionality.

In the initial plusbeta component release, we’re previewing a new capability: the ability to connect web parts and extensions together via a series of dynamic data events.

Dynamic Data – now in plusbeta

Web parts and extensions are frequently developed as packs of functionality that are both designed to work with each other, and work alone as users design their SharePoint pages. To support this flexibility, developers need a consistent way to discover other components within the sample page, and rendezvous these components together to retrieve and share data in an efficient and consistent manner.

To support this, developers can take advantage of the Dynamic Data capability, which provides an event subscription and publishing model. Developers can design and raise various types of events that other components can read and respond to, enabling a flexibility that comes from loosely coupling components together.

To get started, read updated information about SharePoint Framework Dynamic Data APIs you can use.

With both newly released capabilities and a new channel for deploying preview level functionalities, SharePoint Framework continues to focus on delivering features based on your feedback that make it easier to develop and deploy new SharePoint Framework customizations. As you work with any SharePoint feature – and in particular, new beta components – please let us know via GitHub any issues or feedback you may have. Thanks, and happy coding!

Join us on the first Tuesday of every month for the Microsoft Graph API community call. You can download a recurring monthly calendar invite at https://aka.ms/microsoftgraphcall. 

Jeremy Thake, new to the Microsoft Graph team, led a great, interactive call this month with guest speakers including: 

• Casey Burke discussed the PowerApps integration with Microsoft Graph 
• John Liu demoed Microsoft Flow calling the Microsoft Graph 
• Vincent Biret showcased an Online Meetings solution built using the Microsoft Graph 

Thanks to our community contributors: 

• Deluca Giullano– Adding custom data to users Microsoft graph 
• Vlad Catrinescu– Build session download script  
• WaldekMastykarz– Office 365 CLI v1.3.0 

Watch the call here. 

View the presentation here.  

Next month’s call is on Tuesday, July 3, 2018. Submit your questions and topics here. 

Resources: 

From June's call

• Build recap
  • YinaArenas– Introduction to Microsoft Graph(from keynote)
  • YinaArenas– Connect to essential data every app needs 
  • Rob Howard - Create productivity apps in Office 365 
  • VesaJuvenon– SharePoint development  
  • Andrew Bybee – Build the ultimate team hub with Microsoft Teams 
  • Matthew Henderson –Microsoft Graph & Azure Functions 
  • Mark Stafford – Cognitive Services & Microsoft Graph 
  • Channel 9 Build 2018 Microsoft Graph 
  • UWP Kit for Microsoft Graph  
  • Microsoft Graph Community samples 
  • Approval Bot Sample demo 
• John Liu’s bloghttp://johnliu.net/  
• Vincent Biret’s blog http://bit.ly/vince365  
• John Liu’s pull request for Microsoft Flow samples 
• Prefertimezoneas part of request headers  
• hellojshttps://www.npmjs.com/package/hellojs 

Microsoft Graph community call 

• Recurring monthly community call calendar invite - https://aka.ms/microsoftgraphcall 
• Monthly community call topic requests and questions - https://aka.ms/ybuw2i 
• Previous monthly call recordings – Office Development YouTube Channel 

Microsoft Graph feedback 

• Microsoft Graph issues and technical questions - StackOverflow 
• Microsoft Graph recommendations and suggestions - Microsoft Graph UserVoice 

SharePoint Dev Ecosystem / SharePoint Patterns and Practices (PnP) May 2018 update is out with a summary of the latest guidance, samples, and solutions from SharePoint engineering or from the community for the community. This article is a summary of all the different areas and topics around SharePoint Dev ecosystem during the past month.

What is SharePoint Patterns & Practices (PnP)?

SharePoint PnP is a nick-name for SharePoint Dev Ecosystem activities coordinated by SharePoint engineering. SharePoint PnP is community driven open source initiative where Microsoft and external community members are sharing their learning's around implementation practices for SharePoint and Office 365. Active development and contributions happen in GitHub by providing contributions to the samples, reusable components, and documentation.

PnP is owned and coordinated by SharePoint engineering, but this is work done by the community for the community. The initiative is currently facilitated by Microsoft, but already at this point, we have multiple community members as part of the PnP Core team and we are looking to extend the Core team with more community members.

Notice that since this is open source community initiative, there’s no SLAs for the support for the samples provided through GitHub. Obviously, all officially released components and libraries are under official support from Microsoft. You can use SharePoint Developer group in the Microsoft Tech Community for providing input and to ask any questions about the existing materials.

Some key statistics around SharePoint Dev topics from May 2018

• GitHub repository forks at most popular repositories in SharePoint GitHub organization 
  • SP Dev Docs - 356
  • SP Dev FX Web Parts - 636
  • SP Dev Fx Extensions - 136
  • PnP - 2837
  • PnP Sites Core - 480
  • PnP PowerShell - 451
• Unique visitors during past 2 weeks in SharePoint organization repositories - 38,265
• Merged pull requests across SharePoint repositories (cumulative) - 5,121
• Closed issues and enhancements ideas cross SharePoint repositories (cumulative) - 4,206
• SharePoint Online CSOM NuGet package downloads (cumulative) - 530,888
• Page views in SharePoint Dev pages at docs.microsoft.com - 898,005
• Unique tenants using PnP components - 12,350
• Http requests towards SharePoint Online from PnP components (CSOM Core, PowerShell, PnP JS Core) - 9,909,126,368
• SharePoint Dev YouTube channel had 27,491 views with 157,786 minutes watch time

Main resources around SharePoint PnP and SharePoint development

• SharePoint development portal - https://developer.microsoft.com/en-us/sharepoint  
• SharePoint Dev Documentation - http://docs.microsoft.com/sharepoint/dev
• SharePoint Dev Community - http://aka.ms/sppnp - One location for all the resources and news around PnP
• PnP Community Discussions - http://aka.ms/SPDev-Community
• SharePoint Dev Videos on YouTube - http://aka.ms/SPDev-Videos
• Presentations at SlideShare
  
  

June 2018 monthly community call

Agenda for the Tuesday 11th of June 2018 SharePoint Dev Ecosystem / Patterns and Practices community call at 8 AM PST / 5 PM CEST:

• Monthly summary of SharePoint Development topics - Latest SharePoint roadmap and community news - Vesa Juvonen (Microsoft) ~20 min
• Introduction of new fluent API for Taxonomy services with PnPjs - Patrick Rodgers (Microsoft) ~15 min
• Introduction of the SharePoint Starter Kit - Vesa Juvonen (Microsoft) ~15 min
• Q&A ~10 min

Monthly community call will get recorded and release to PnP YouTube channel typically within 24 hours after the recording is ended. If you have any questions, comments or feedback, please participate in our discussions in the Microsoft Tech Community under SharePoint developer group. 

SharePoint Dev Blog posts

Here are the latest blog posts and announcements around SharePoint development topics from dev.office.com/blogs.

• 6th of June - Announcing SharePoint Framework 1.5: new tools and a beta preview
• 4th of June - New SharePoint CSOM version released for SharePoint Online - May 2018
• 10th of May - Updates from Build: new improvements for SharePoint Framework coming soon
• 10th of May - SharePoint Dec Community (PnP) - May 2018 monthly community call recording
  
  

PnP Webcasts

We started new PnP Webcasts are typically 15-30 min long conversational webcasts around a specific topic. This series was started in October 2015 and have continued releasing new videos since. All new webcasts are released on PnP YouTube Channel. Here are the new webcasts released after the last monthly release. We are looking into continuing the releases of the webcast in the future using weekly or bi-weekly schedule depending on the topics to be covered.

• 14th of May - Activation options for SharePoint Framework extensions
• 30th of April - Consuming taxonomy within SharePoint Framework solution
  
  

General Dev, CSOM, PnP Core, PnP PowerShell SIG Bi-Weekly Call Special Interest Group (SIG)

General SP Dev, CSOM PnP Sites Core, PowerShell and Provisioning Special Interest Group (SIG) have bi-weekly meetings to cover the general SharePoint topics, CSOM and latest in the PnP CSOM core component, PnP PowerShell and in the PnP remote provisioning engine. These calls have also free Q&A section if you have any questions about SharePoint development in on-premises or in the cloud. Need to get a recommendation for your design or having a hard time with some APIs? - Drop by, ask a question and we'll help you.

You can download invite for the bi-weekly meeting from the following location. 

• Invite to bi-weekly call - https://aka.ms/sppnp-core-sig-call

All SIG meetings are being recorded and are available for view from PnP YouTube Channel. Here are the latest recordings of the SIG calls.

• 31st of May - SP Dev news with engineering update. Recap of SharePoint developer announcements from SharePoint Conference 2018. Microsoft Flow and PowerApps demos from SPC 2018.
• 17th of May - SP Dev news with engineering update. Microsoft Flow and PowerApps from the context of SharePoint
• 3rd of May - SP Dev news with engineering update. Modernizing SharePoint sites - open source tooling. Add-in submission process with AppSource.

Interested in doing a community demo in these community calls? - Please let us know!

SharePoint Framework (SPFX) and JavaScript Special Interest Group (SIG)

SharePoint Framework and JavaScript Special Interest Group (SIG) has bi-weekly meetings to cover latest changes in the SharePoint Framework side, from the engineering perspective and to cover also latest development related to the PnP JS Core library. These calls are designed to have 50%/50% of content and demos and there has been already great community demos on the new SharePoint Framework Client-side web parts. If you're interested in showing your code, just let us know.

• Invite to bi-weekly call - https://aka.ms/sppnp-js-sig-call
• Gitter (Around the PnP JS Core) - https://gitter.im/OfficeDev/PnP-JS-Core

All SharePoint Framework and JS SIG meetings are recorded, so that you can check the demos and discussions if you can't make the actual call. You can find the latest recordings from the PnP YouTube Channel. Here are the latest recordings.

• 7th of June - SharePoint Framework engineering update, PnP JS Core update, Office 365 CLI update, SPFx controls update - Dynamic Data in SharePoint Framework v1.5. Using Jest Test Framework with SharePoint Framework solutions.
• 24th of May - SharePoint Framework engineering update, PnP JS Core update, Office 365 CLI update, SPFx controls update - News from the SharePoint Conference 2018
• 10th of May - SharePoint Framework engineering update, PnP JS Core update, Office 365 CLI update, SPFx controls update - Demos from MS Build 2018. Building Student Budget planning tool

Interested in doing a community demo in these community calls? - Please let us know!

SharePoint Dev Ecosystem in GitHub

There are quite a few different GitHub repositories under the SharePoint brand since we wanted to ensure that you can easily find and reuse what's relevant to you. We do also combine multiple solutions to one repository so that you can more easily sync and get latest changes to our released guidance and samples. 

• sp-dev-docs - Source for new SharePoint dev center documentation exposed from http://dev.office.com/sharepoint
• sp-dev-fx-webparts - Client-side web part samples from community and engineering
• sp-dev-samples - Samples for add-ins, webhooks, and other API
• sp-dev-fx-extensions - Samples and tutorial code around SharePoint Framework Extensions
• sp-dev-fx-vs-extension - Open source Visual Studio IDE extension for creating SharePoint Framework solutions in the Visual Studio 2015 or 2017
• sp-dev-build-extensions - Different build extensions like gulp tasks and gulp plugins from the community and engineering around SharePoint development
  
• sp-dev-gdpr-activity-hub - Reference solution on the GDPR business case showing SPFx implementation with PowerBI and modern site customization
• sp-dev-solutions - Repository for more polished and fine-tuned reusable solutions build with SharePoint Framework
• sp-dev-fx-controls-react - Reusable content controls for SharePoint Framework solutions build with React
• sp-dev-fx-property-controls - Reusable property pane controls to be used in web parts
• sp-dev-list-formatting - Open-source community driven repository for column and view formatting JSON definitions
• sp-dev-site-scripts - Open-source community driven repository for community Site Designs and Site Scripts
• sp-starter-kit - Starter kit solution for SharePoint modern experiences

• PnP - Main repository for SP add-in, Microsoft Graph etc. samples
• PnP-Guidance - Guidance, presentations, and articles which are partly synced to MSDN
• PnP-Sites-Core - Office Dev PnP Core component
• PnP-JS-Core - Office Dev PnP Core component for JavaScript
• PnP-PowerShell - Office Dev PnP PowerShell Cmdlets
• PnP-Tools - Tools and scripts targeted more for IT Pro's and for on-premises for SP2013 and SP2016
• PnP-Partner-Pack - Packaged guidance with detailed instructions on setting things up in Office 365 and in Azure.
• PnP-Transformation - Material specifically for the transformation process. Currently, includes samples around InfoPath replacement and transformation tooling from farm solutions to add-in model.
• PnP-Provisioning-Templates - Source for templates available from PnP Template Gallery at http://templates-gallery.sharepointpnp.com
• PnP-Provisioning-Schema - PnP Provisioning engine schema repository
• PnP-IdentityModel - Open source replacement of Microsoft.IdentityModel.Extensions.dll
  
  
• PnPjs - PnPjs Framework repository
  
  

What's supportability story around PnP material?

Following statements apply across all of the PnP samples and solutions, including samples, core component(s) and solutions, like PnP Partner Pack.

• PnP guidance and samples are created by Microsoft & by the Community
• PnP guidance and samples are maintained by Microsoft & community
• PnP uses supported and recommended techniques
• PnP implementations are reviewed and approved by Microsoft engineering
• PnP is open source initiative by the community – people who work on the initiative for the benefit of others, have their normal day job as well
• PnP is NOT a product and therefore it’s not supported by Premier Support or other official support channels
• PnP is supported in similar ways as other open source projects done by Microsoft with support from the community by the community
• There are numerous partners that utilize PnP within their solutions for customers. Support for this is provided by the Partner. When PnP material is used in deployments, we recommend being clear with your customer/deployment owner on the support model
  
  

Latest changes

SharePoint Starter Kit

SharePoint Starter Kit demonstrates how to extend out of the box modern experiences in the SharePoint. It demonstrates multiple different techniques and uses different patterns and practices to build end-to-end demonstration solution which can be provisioned to any Office 365 tenant. It contains for example following capabilities, which you can learn from or use them as your reference:

• How to provision site collections using PowerShell
• How to apply content and layouts to site collections
• How to create and use Site Designs and Site Scripts
• How to build custom web parts and extensions for your deployment
• 15 different ready to use web parts
• 7 different extensions
• Hub site configuration
• etc. etc. etc.

SharePoint Starter Kit was announced in SharePoint Conference 2018 and we will keep on evolving and update this reference solution also during future releases. We also do welcome contributions on this open-source community lead project.

SharePoint Framework samples 

These are samples which are available from the SharePoint client-side web part sample repository at https://github.com/SharePoint/sp-dev-fx-webparts or from the SharePoint Framework Extensions repository at https://github.com/SharePoint/sp-dev-fx-extensions.  

• New sample react-reduxform which demonstrate the use of Redux-Form library with SPFx, React and Typescript. Demonstrates how to easily build a dynamic grid using redux-form.
• New sample react-jest-testing which shows how to use Jest Testing Framework with a SPFx client-side solution
• New sample angularelements-helloword which illustrates how to use Angular Elements in the SharePoint Framework
• New sample react-events-dynamicdata which illustrates how to use dynamic data capability which was released in SharePoint Framework 1.5 
• New sample react-calendar-feed which shows how to connect to different data feeds and render consistent calendar look and feel
• New sample react-designpatterns-typescript which shows different design patterns applied to SharePoint Framework solution
  
  
• Updates to SiteDesignStudio solution, which provides a web part to create Site Designs and Site Scripts for your tenant
• Updates to react-search-refiners which shows you how to build user-friendly SharePoint search experiences using Office UI fabric tiles
• Updates to react-content-query-webpart which shows how to build a content by query web part using SharePoint Framework
  
  
• New react-application-injectcss application customizer showing how to inject a custom Cascading Style Sheet (CSS) on modern pages. 
• Multiple extensions updated to use latest SharePoint Framework 1.4 or v1.5 version and cleaning in existing SharePoint Framework extension samples
  
  

Reusable open source controls for SharePoint Framework

New reusable controls initiative was announced in Ignite 2017 during September. There are two npm packages and source code repositories for the reusable controls which you can use in your SharePoint Framework solutions. We do welcome community contributions to these initiatives as well. There are two different repositories: sp-dev-fx-property-controls and sp-dev-fx-controls-react. Here are the changes on these repositories.

Added

• SecurityTrimmedControl control got added #74

Enhancements

• Allow the TaxonomyPicker to also be used in Application Customizer #77
• Add npm postinstall script to automatically add the locale config #78

Fixes

• Icon not showing up in the Placeholder control #76
  
  

Community list formatting definitions

SharePoint Columns Formatting capability was released for First Release customers during October 2017. As part of the availability, we also announced the availability of open source repository for sharing different column formatting definitions. Since we will be releasing also new view formatting capability soon, the repository has been renamed as sp-dev-list-formatting as it will be containing both view and column formatting samples.

• No new column formatting samples during May
  
  

Community Site Designs and Site Scripts

SharePoint Site Designs and Site Scripts has been released for production usage during March 2018. As part of the availability, we also announced the availability of open source repository for sharing different Site Designs and Site Scripts. Following lists the changes in the Site Design and Site Script area.

• No new Site Designs or Site Scripts during May, but adjustments and improvements on existing ones.
  
  

Office 365 CLI 

Office 365 CLI was released in November 2017. This is an open source tool which enables you to controls tenant level properties in SharePoint Online or in Office 365. This is an alternative options for setting management on top of existing PowerShell cmdlets.

v1.3.0 release available with following changes

Added

• spo file copy - copies a file to another location #286
• spo folder add - creates a folder within a parent folder #425
• spo folder copy - copies a folder to another location #424
• spo folder get - gets information about the specified folder #427
• spo folder list - returns all folders under the specified parent folder #428
• spo folder remove - deletes the specified folder #426
• spo hidedefaultthemes get - gets the current value of the HideDefaultThemes setting #341
• spo hidedefaultthemes set - sets the value of the HideDefaultThemes setting #342
• spo site o365group set - connects site collection to an Office 365 Group #431
• spo theme apply - applies theme to the specified site #343

• graph groupsetting add - creates a group setting #443
• graph groupsetting get - gets information about the particular group setting #450
• graph groupsetting list - lists Azure AD group settings #449
• graph groupsettingtemplate get - gets information about the specified Azure AD group settings template #442
• graph groupsettingtemplate list - lists Azure AD group settings templates #441
• graph user sendmail - sends e-mail on behalf of the current user #328

Changes

• added support for re-consenting the AAD app #421
• added update notification #200
• extended the 'spo app deploy' command to support specifying app using its name #404
• extended the 'spo app add' command to return the information about the added app #463
  
  

PnP CSOM Core and Provisioning Engine

PnP CSOM Core component is a wrapper on top of native SharePoint CSOM and REST API, which simplifies complex scenarios with remote APIs, one of the example is the PnP Provisioning Engine for remote templates. The first version of the PnP remote provisioning engine was released with the May 2015 release. This list contains the main updates in this release:

Added

• Added optional timeout value on AppManager.Add method
• Support version 1.4 of page header data structure
• Feature/file folder async extension methods [baywet]

Changed

• ClientComponentId and ClientComponentProperties are now updated when applying a template to a site where the custom action already exists [SchauDK]
• Fixes issue with requiring tenant admin access while not provisioning tenant scoped artifacts
• Fixed issue where a list would not be created based on a list template (TemplateFeatureId)
• Fixes issue with double tokens in content by search web part provisioning [KEMiCZA]
• Fixes issue with site designs not correctly being associated with web template
• Fixes issue where you could not specify content type in a datarow element in a provisioning template
• Fixes issue where you tried to modify a property of a default modern homepage and all web parts disappeared
• Fixed issue with Security Group names including HTML links [jensotto]
• Fixed issue with UseShared property for Navigation Settings [TheJeffer]
• Fixed issue with not existing links in Navigation Settings [gautamdsheth]
• Updated Microsoft Graph SDK package to version 1.9.0
• Correctly extract modern page title [SchauDK]
• Fixes issue with using culture in page header persisting [guillaume-kizilian]
• Fixes lookup column support by supporting list web relative URLs [stevebeauge]
• Fixed ClientSidePageHeaderType enum inconsistency [SchauDK]
• Fixing #1770 issue. Now we are considering Publishing Images field type [luismanez]
• #1804 Incorrect exception thrown while setting multi-valued tax field [gautamdsheth]
• Typo fixes [stwel]

See also https://testautomation.sharepointpnp.com for day-to-day results and executed tests.

PnP JavaScript Core Library - PnPjs

Latest update is version 1.1.0 on the PnPJs library. Here's are the latest changes since the previous monthly release. Notice that if you are using old pnp-js-core, we highly recommend upgrading to the new PnPjs.

Added

• @pnp/sp-taxonomy: Added new library to support fluent queries against SharePoint Taxonomy data
• @pnp/sp-clientsvc: Added new library with fluent API base classes for client.svc based requests
• @pnp/common: Added utility method sanitizeGuid and getAttrValueFromString
• @pnp/odata: Added LambdaParser that takes any function to handle parsing Response
• tooling: Added --stats flag to gulp package to output webpack stats during bundle

Fixed / Changed

• @pnp/odata: Fixed bug in BufferParser
• tooling: Fixed bug in serving individual packages using --p
• @pnp/sp: fixed issue in generated js files where $$VERSION$$ placeholder was not replaced correctly
• @pnp/graph: Disallowed caching of non-GET requests
• tooling: Fixed docs-clean ordering issue so everything is clean before other tasks run
  
  
• @pnp/nodejs: Updated how global shims are set for Request types (Headers, Response, Request)
• @pnp/odata: Changes to request pipeline to support sp-clientsvc (non-breaking)
• @pnp/odata: Remove public get from abstract class Queryable (non-breaking)
• @pnp/sp: Added exports for toAbsoluteUrl and extractWebUrl utility methods
• @pnp/logging: Changed default LogLevel to Info for write and writeJSON
• build: Added preserveConstEnums flag to tsconfig.json
• docs: Small formatting changes, added anchors to headings in html to ease linking
• all: Updated package.json dependencies in root and individual packages
• docs: Updates to docs, added section on sp-taxonomy and sp-clientsvc libraries

Removed / Deprecated

• @pnp/sp: Removed unused APIUrlException class
• @pnp/nodejs: Removed packaging step to webpack bundle, no need for node and reduces package size
  
  
• @pnp/common: Deprecated exported static Util class. Migrate to using the individually exported methods
  
  

This is a similar effort as what PnP initiative previously has done with the PnP CSOM Core Component together with the community. 

PnP PowerShell

PnP PowerShell providers more than three hundred additional PowerShell cmdlets, which can be used to manipulate content in SharePoint Online and in on-premises (SP2013, SP2016). These cmdlets are additive for SharePoint Online management shell, which concentrate more on the administrative tasks with SharePoint Online. 

Here are the latest changes in the PnP PowerShell

Added

• Added Grant-PnPTenantServicePrincipalPermission to explicitly grant a permission on a resource for the tenant.

Changed

• Fixed edge cases where progress sent to PowerShell would be null, causing the provisioning of a template to end prematurely.
• Fixed Unregister-PnPHubSite where you could not unregister a hub site if the site was deleted before unregistering

Other

• Updated automatically generated PnP PowerShell cmdlet documentation at docs.microsoft.com
  
  

PnP sample library

Here are updates across the PnP code sample library by the community on the code and documentation, which is a great way to contribute as well.

• New sample Provisioning.CreateSite.Mvc which shows how to use OfficeDevPnp core component to create subsites or new site collections using MVC 5 and a provider hosted add-in
  
  
• Updates toSharePoint.Modernization tool which can be used to batch updated classic pages to modern pages
• Updates to SharePoint.Scanning which is a framework to implement multi-threaded queries in SharePoint Online
• Updates to SharePoint.UIExperience.Scanner tool which can be used to detect where classic and modern capabilities are used in your tenant
• Updates to SharePoint.Visio.Scanner tool which can be used to detect where Visio Web Access is used in your tenant
  
  
• Updates to Visual Studio extension for SharePoint Framework to support SharePoint Framework 1.5
  
  

SharePoint Dev articles 

SharePoint Dev articles are surfaced currently in docs.microsoft.com/en-us/sharepoint/dev. ´Since the last release, we have now merged also SharePoint PnP Solution guidance to docs.microsoft.com platform, so you'll only have one location to follow all relevant SharePoint Dev documentation and guidance. You can provide contributions to these documents by submitting documentation improvements using GitHub tooling. All of the SharePoint Dev docs are stored and surfaced from the sp-dev-docs repository. 

Here are new/updated articles on the SharePoint Development. 

• Try SharePoint Framework preview capabilities
• Connect SharePoint Framework components using dynamic data
• Hide a web part from the toolbox
• Commanding within a web part - Design guidance
• Empty state of a web part - Design guidance
• Key web part examples - Design guidance
• Updated SharePoint Framework roadmap
• Updated Site design JSON schema
• Updated Debug SharePoint Framework solutions in Visual Studio Code
• Updated Scaffold projects by using Yeoman SharePoint generator 
• Updates to transformation your classic SharePoint sites article series
• • Modernize your classic SharePoint sites
  • Modernize the user interface
  • Maximize your use of the modern list and library user interface
  • Modernize the customizations
  • Connect to an Office 365 group
  • Modernize the site branding
    
• Numerous other adjustments and updates based on input from the community
  
  

PnP Guidance videos 

You can find all SharePoint Dev videos on our YouTube Channel at http://aka.ms/sppnp-videos. This location contains already a significant amount of detailed training material, demo videos, and community call recordings. 

• No specific guidance videos on top of the community call demos during this month
  
  

Key contributors to the June 2018 update

Here’s the list of active contributors (in alphabetical order) since last release details in SharePoint Dev repositories or community channels. PnP is really about building tooling and knowledge together with the community for the community, so your contributions are highly valued across the Office 365 customers, partners and obviously also at Microsoft.

Thank you for your assistance and contributions on the behalf of the community. You are making a difference!

• Alex Terentiev (SharePointalist) - @alexaterentiev
• Andrew Connell (Voitanos) - @andrewconnell
• Andrew Koltyakov (ARVO Systems) - @andrewkoltyakov
• Charles Simard-Lecours - cslecours
• Chris Kent (DMI) - @theChrisKent
• Elio Struyf - @eliostruyf 
• Erwin van Hunen (Rencore) - @erwinvanhunen 
• Eric Shupps - @eshupps
• Franck Cornu (aequos) - @FranckCornu
• Fredrik Thorild - thorild
• Gautam Sheth (Rapid Circle) - @gautamdsheth
• guillaume-kizilian alias - guillaume-kizilian
• gunna025 alias - gunna025
• Hugo Bernier - hugoabernier
• Janhavi - spcrux
• Laurent Sittler (Exakis) - @laul0_68
• Luis Valencia - @levalencia
• Massimo Prota (Rapid Circle) - @massimoprota
• Michael Schau - @SchauDK
• Mikael Svenson (Puzzlepart) - @mikaelsvenson
• nilsvbconxion alias - nilsvbconxion
• Ole Kristian Mørch-Storstein (Puzzlepart) - @ole_kristian
• Paolo Pialorsi (PiaSys.com) - @PaoloPia
• Paul Pascha (Wortell) - @paulpascha
• Paul Schaeflein - @paulschaeflein
• Radi Atanassov (OneBit Software) - @RadiAtanassov
• Raul Garita Ch (Buildingi) - rgarita
• Simon-Pierre Plante (SPP Technologies) - spplante
• Spencer Harbar (ClearPeople) - @harbars
• Stefan Bauer (n8d) - @StfBauer
• Steve Beaugé (Solutions pour SharePoint) - @stevebeauge
• Stoyan Grigorov - stwel
• Velin Georgiev - @velingeorgiev
• Vincent Biret (2toLead) - @baywet
• Vipul Kelkar (Rapid Circle) - vipulkelkar
• Waldek Mastykarz (Rencore) - @waldekm
• Yannick Plenevaux - @yp_code
  
  

Companies: Here's the companies, which provided support for PnP initiative for this month by allowing their employees working for the benefit of others in the PnP initiative. There were also people who contributed from other companies during last month, but we did not get their logos and approval to show them in time for these communications. If you still want your logo for this month's release, please let us know and share the logo with us. Thx.

 

 

 

 

 

 

 

SharePoint monthly community call is our monthly event for SharePoint developers to stay up to date on the latest changes to SharePoint Dev topics from engineering and community perspective. This monthly community call is on every second Tuesday of each month where we go through a summary of SharePoint Development engineering news, latest guidance, status in UserVoice, community contributions and other relevant topics. 

You can also check the latest updates from the monthly summary at dev.office.com/blogs.
You can download a recurrent invite for these monthly calls from http://aka.ms/spdev-call.

This is the recording of SharePoint Dev Ecosystem / Patterns and Practices (PnP) monthly community call from Tuesday 12th of June 2018. Here's used agenda with direct links to specific sections, if you want to directly jump to a specific topic (will redirect your browser to SharePoint Dev YouTube Channel).

• Latest SharePoint community metrics from May 2018 (YouTube, GitHub etc.) -  4:15
• Top 10 UserVoice entries for SharePoint Dev and quick status - http://aka.ms/spdev-uservoice - 9:58
• Summary of May 2018 Release - Summary of released materials around SharePoint Development since last monthly call - 11:58
• Community contributors and companies which have been involved within past month - 15:04
• New PnP Core Team members - Chris Kent and Stefan Bauer - 17:13
• SharePoint Starter Kit for modern experiences - 20:44
• A quick look at the SharePoint Developer roadmap - 25:06
• SharePoint Framework 1.5 content - 26:37
• Plans SharePoint Framework 1.6 - Currently planned capabilities - 26:59
  
  
• Demo - SharePoint Starter Kit - What's available and how to get started - Vesa Juvonen (Microsoft) - 29:33
• Demo - PnPjs and fluent API for SharePoint Taxonomy data - Patrick Rodgers (Microsoft) - 42:29

Full recording - available from SharePoint Developer YouTube channel - http://aka.ms/spdev-videos.

Presentation slides used in the call

Additional resources

Additional resources on covered topics and discussions.

• SharePoint Development June 2018 monthly summary
• SharePoint Starter Kit
• PnPjs Library
  
  
• Recurrent invite to SharePoint Development monthly calls - http://aka.ms/spdev-call
• SharePoint Developer documentation - http://aka.ms/spdev-docs
• SharePoint Development Issues - http://aka.ms/spdev-issues
• SharePoint GitHub organization - http://github.com/SharePoint
• SharePoint Development UserVoice - new feature requests - http://aka.ms/spdev-uservoice
  
  

"Too many links, can't remember" - not a problem... just one URL is enough with http://aka.ms/sppnp.

“Sharing is caring”

SharePoint Team, Microsoft  - 13th of June 2018