Blog

SharePoint PnP Customer Story - Using PnP Partner Pack at Weleda AG

Thu, 06 Oct 2016 10:00:00 GMT

In this SharePoint PnP Customer Story we concentrated on covering how Experts Inside delivered a self-service site collection provisioning solution for Weleda AG, by using the PnP Partner Pack as a starting point for their delivery. Customer wanted to provide automated process for their employees to have branded collaboration sites and PnP Partner Pack starter kit provided excellent starting point for the Experts Inside for this customer case.

PnP Partner Pack is ready-to-use starter kit, which provides typical self-service site collection provisioning capabilities for end users at site collection and in sub site level. You can us it as such or it can be also customized based on the functional and business requirements. PnP Partner Pack also includes additional capabilities like governance automation as backend services, having standard template available for site creation cross SharePoint Online tenant and to enable responsive UI with classic SharePoint sites automatically when sites are provisioned.

PnP Partner Pack is open source, community driven solutions which is part of the SharePoint PnP initiative. SharePoint PnP initiative is owned and coordinated by SharePoint engineering, but work happens together with the tens and tens of community members. You can find PnP Partner Pack and additional details from dedicated PnP Partner Pack repository at GitHub.

Presentation section covers following topics

Introduction to customer - Weleda AG
What were the customer requirements and solution architecture with PnP assets
Customer specific customizations build on top of the reusable solutions and components from PnP
- Yammer extensibility handler for associating Yammer groups automatically to SharePoint sites
- Yammer web part replaced automatically to newly created SharePoint sites
- Scheduled backend service (Azure WebJob), which synchronizes group memberships between SharePoint and Yammer groups

Webcast demo shows following details

Customized PnP Partner Pack used at Weleda AG
Changed branding and modifications on the standard UIs in the PnP Partner Pack
Configuration in Azure side for enabling backend services for self-service site collection creation
How standardized collaboration sites are looking after they've been provisioned automatically using the PnP provisioning engine
Responsive UI package applied to classic SharePoint sites

Video presenters: Nicki Borell, Kevin Mees, Vesa Juvonen

Video at YouTube.

Additional resources

See following resources around the covered topics and mentioned resources.

Weleda customer case at Microsoft Customer Stories
PnP Partner Pack in GitHub - Source code and installation details
PnP Webcast - Introduction to PnP Partner Pack v2.0

Notice. This particular deployment was done using PnP Partner Pack v1.0, but the newer version has significant amount of additional ready to use capabilities.

What is SharePoint / Office DevPatterns & Practices (PnP)?

PnP is 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 (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 for 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 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 around PnP program or this blog post, please use the Microsoft Tech Community (SharePoint Developer group).

“Sharing is caring”

Vesa Juvonen, Senior Program Manager, SharePoint, Microsoft - 6th of October 2016

PnP Templates Gallery - Open source provisioning templates

Tue, 04 Oct 2016 10:00:00 GMT

At Microsoft Ignite 2016, in Atlanta, we proudly announced the availability of the new “PnP Templates Gallery” portal, which is available at the following URL: https://templates-gallery.sharepointpnp.com.

The basic idea around this new portal, is to have a public and shared repository for PnP provisioning templates, which anybody can download and use for free. Moreover, we hope that many community members will like to share their own templates with the community. In the following figure, you can see the home page of the PnP Templates Gallery.

The site is responsive and mobile-aware, and allows you to browse the templates, and to search for them based on few search criteria:

Category: see later what are the available categories
Target platform: can be SharePoint Online, SharePoint 2016, or SharePoint 2013
Scope: defines whether the template targets the root web of a Site Collection, a sub web, or it is a partial template that can be applied on any site
Rating: there is a rating model with values between 1 and 5 stars, which is based on the community feedbacks

About the categories, so far we decided to group templates into the following families:

Accounting
Business
Collaboration
Development
Document Management
Human Resources
IT Management
Others

Once you found a template that you like, you can simply download the .PNP Open XML package file and use it in your own environment or tenant. As you will see later in this article, the templates can also be used within the fresh new PnP Partner Pack 2.0.
At the time of writing this article, there are just a few templates available in the gallery. However, we do believe that soon there will be a lot of contents, thanks to the contribution from the whole community of Office 365 developers.

How to use the templates

If you simply want to use the templates, without having any additional components or tools in your environment, you can simply download the .PNP file from the detail page related to your chosen template.

Once you have downloaded the .PNP file, you can easily apply it to any target site just using the PnP PowerShell extensions, which are available together with setup instruction at the following URL: https://github.com/OfficeDev/PnP-PowerShell.

For example, let assume that you have downloaded the “Curriculum Vitae Database” template (https://templates-gallery.sharepointpnp.com/template/curriculum-vitae-database). By using the following PowerShell syntax, you will be able to apply the template to a target site.


Connect-SPOnline http://<your-tenant>.sharepoint.com/sites/<your-target-site>
Apply-SPOProvisioningTemplate .\CVDatabase.pnp

Of course, you can also decide to customize the template before applying it to any target. It is a common PnP Provisioning Template, and you can do whatever you want with it.

Integration with the PnP Partner Pack 2.0

Nevertheless, one of the biggest news related to the PnP Templates Gallery is the native integra-tion with the PnP Partner Pack 2.0. If you don’t know anything about the PnP Partner Pack, you should browse to the following site: http://aka.ms/OfficeDevPnPPartnerPack. There you will find detailed information, and a setup guide to deploy the PnP Partner Pack in your own Office 365 tenant.

The PnP Partner Pack is a sample reference solution, provided by PnP as an open source and com-munity project, that shows how to manage at a business-level the capabilities offered by the PnP Provisioning Engine. We define it a reference solution, because you can use it “as is” or you can customize it, extending its basic idea. Whatever will be your choice, the PnP Partner Pack allows you to see how you should implement some common scenarios and you can satisfy customers’ requirements, adhering to the patterns and practices that we promote as PnP.

The main capabilities of the PnP Partner Pack v. 2.0 are:

Self-service site collection and sub site provisioning solution
- Fully configurable based on business requirements
- Save existing site as new template from the standard user interface
- Template creation does not require xml or script knowledge - New templates can be generated from the existing sites
- Sub site creation implementation with remote provisioning
- Support for tenant wide or site collection templates
Responsive UI package for the Office 365 SharePoint sites
- Uses JavaScript and custom CSS files to transform OOB SharePoint sites as respon-sive
- Can be applied to any SharePoint site and does not depend on the PnP Partner Pack
UI widget implementations with JavaScript embedding pattern to avoid custom master pages
Governance tools for administrators: apply SharePoint farm-wide branding, refresh site templates, bulk creation of site collections
Reference governance remote timer jobs (Azure WebJobs) to perform typical enterprise governance operations to existing site collections and sites
Configurable branding and text elements for easy branding element changes

When your end users create a new site collection or a new sub-site, using the PnP Partner Pack v. 2.0, they will be able to select a template that is consumed directly, via a set of REST API, from the PnP Templates Gallery. In the following figure, you can see the user interface of the PnP Partner Pack, while selecting the template to apply.

As you can see there is a drop-down list through which you can select to search for templates in the PnP Templates Gallery. Thus, if the gallery will become full of interesting templates, you will be able to make them directly available to your end users, simply by installing the PnP Partner Pack in your tenant.

Of course, if you don’t like to allow your end users to freely search on the gallery, you can disable that capability just changing a setting in the PnP Partner Pack. Eventually you will be still able to download from the gallery the templates that you like, and make them available in your tenant with a manual upload in the PnP Partner Pack Infrastructural Site Collection.

How to contribute?

To achieve the intended result with the PnP Templates Gallery, it is fundamental to have great contributions from the community, that mean from you, too.

Thus, if you like to submit your templates and ideas, you can simply go to the GitHub repository (https://github.com/OfficeDev/PnP-Provisioning-Templates), which sits under the cover of the gallery, and follow the “Templates Publishing Guidelines”.

You will need to select the matching category for your template, create a .PNP template file, con-figure some properties of the template, provide a README.md file for the template, and submit a Pull Request for your new contribution. Upon approval, your template will become available in the gallery, and you will be credited for your great job in favor of the community.

Wrap up

We, as the PnP Core Team, are really excited about the potential of the new PnP Templates Gallery, together with the release of the PnP Partner Pack 2.0. We hope that you will enjoy the idea and that - if possible - you will also actively contribute to the growth of the gallery.

“Sharing is caring”

Author - Paolo Pialorsi, Senior Consultant, Piasys.com, PnP Core team member

Editor - Vesa Juvonen, Senior Program Manager, SharePoint, Microsoft

4th of October 2016

SharePoint PnP Webcast – CRUD operations with SharePoint Framework client-side web parts

Mon, 03 Oct 2016 10:00:00 GMT

In this PnP Webcast we concentrated on covering how to perform typical CRUD (Create, Read, Update, Delete) operations with different JavaScript framework with SharePoint Framework client-side web parts. Webcast concentrates on covering considerations and practices on performing basic operations without any framework, with Angular 1.x, with React or with PnP JS Core library. You can find related sample code from SharePoint Framework client-side web part sample repository, which is also open for community contributions.

Notice. When this webcast was released, SharePoint Framework was available as a Developer Preview release.

Presentation covers following topics:

Introduction to covered frameworks: No Framework, PnP JS Core, Angular, React
Considerations on using different frameworks in client-side web parts

Web cast demo shows following details

Demonstration of the provided web parts from reference solution. UI is as simple as possible by design, so that there's no additional complexity on the code
Clarifications on what to consider when using a specific JavaScript framework in your web part
Comparison of the code when you are using different frameworks

Webcast presenters: Waldek Mastykarz, Vesa Juvonen

Presentation used in this web cast is available from http://docs.com/OfficeDevPnP.

Video at YouTube.

Additional resources

See following resources around the SharePoint Framework.

What is SharePoint / Office DevPatterns & Practices (PnP) web cast series?

SharePoint / Office Dev Patterns & Practices (PnP) webcast series covers different patterns, practices and topics around development with Office 365 and SharePoint. Majority of the topics are valid for the Office 365 and SharePoint on-premises. Our objective is to release new around 30 minute long web cast each Monday with few slides and a live demo on the covered topic. All web casts are published at the PnP YouTube channel with additional references on the existing materials.

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

“Sharing is caring”

Vesa Juvonen, Senior Program Manager, SharePoint, Microsoft - 3rd of October 2016

Microsoft Graph findMeetingTimes API update

Fri, 30 Sep 2016 07:44:00 GMT

Hi all, we want to give you a heads up on some changes that are coming to the findMeetingTimes API which has been available in preview in Microsoft Graph. We are making these changes to further improve the API based on feedback, and these changes will be widely deployed over the next few weeks. The updated API will be available in the /beta and subsequestly in the /v1.0 endpoint as we make the feature generally available.

In summary, the changes are as follows:

1. Names of the following complex types, properties and parameters are updated:

2. The timeSlot parameter changed from type microsoft.graph.timeStamp to type microsoft.graph.dateTimeTimeZone.

3. A new parameter minimumAttendeePercentage’ is being added. This is an optional parameter that indicates the minimum percentage of available attendees required for the API to return suggestions. Input values for this parameter should be of type Double and can range from 0 to 100.

The complete schema looks like below:

</Action>

</ComplexType>

</ComplexType>

</ComplexType>

The API now requires one of the two scopes - Calendars.Read.Shared OR Calendars.ReadWrite.Shared.

Please note that this is a breaking change, and if your app uses the findMeetingTimes (Preview) API, the app needs to be updated to accommodate these changes. Once the changes have been fully deployed worldwide (4-6 weeks), your app can start using the new schema via the “findMeetingTimes” API. In the meantime, if your app is using the API at the /beta endpoint, users might experience intermittent issues when accessing the API through your app. We have also made the old schema available to you through the ‘findMeetingTimesOld’ API. The ‘findMeetingTimesOld’ API will be available through the deployment period and will be retired shortly after the schema changes are fully deployed.

More extensive documentation on the new functionality is coming soon in our API reference documentation page. Please let us know if you have any questions, and visit http://graph.microsoft.io for more information on APIs available.

Thank you and happy coding

Shreedevi Padmasini on behalf of the Microsoft Graph and Outlook teams

New SharePoint CSOM version released for SharePoint Online - September 2016

Thu, 29 Sep 2016 18:00:00 GMT

We are happy to announce 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 again contains few updates on the existing SharePoint CSOM assemblies and some maintenance changes. These monthly changes are not significant, but we want to align on the monthly rythm in future, so that you can know beforehand that there will be new version arriving during end of each month.

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 on latest version, rather than downloading the SDK to your machine.

Version of the newly released CSOM package is 16.1.5715.1200. Previous versions of the NuGet has 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.5715.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.

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 is clarified in following blog post - Using correct Client Side Object Model (CSOM) version for SharePoint customizations.

New properties and methods cross assemblies

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

Microsoft.SharePoint.Client

public property Microsoft.SharePoint.ApplicationPages.ClientPickerQuery.ClientPeoplePickerQueryParameters.QuerySettings
public property Microsoft.SharePoint.ApplicationPages.ClientPickerQuery.PeoplePickerQuerySettings.ExcludeAllUsersOnTenantClaim
public property Microsoft.SharePoint.ApplicationPages.ClientPickerQuery.PeoplePickerQuerySettings.TypeId

public property Microsoft.SharePoint.Client.ChangeItem.EditorLoginName
public method Microsoft.SharePoint.Client.FolderCollection.AddUsingPath
public property Microsoft.SharePoint.Client.List.LastItemUserModifiedDate
public property Microsoft.SharePoint.Client.PickerSettings.QuerySettings
public class Microsoft.SharePoint.Client.RecycleBinQueryInformation

public method Microsoft.SharePoint.Client.Web.GetRecycleBinItemsByQueryInfo
public property Microsoft.SharePoint.Client.Web.LastItemUserModifiedDate
public property Microsoft.SharePoint.Client.Web.NotificationsInOneDriveForBusinessEnabled
public property Microsoft.SharePoint.Client.Web.NotificationsInSharePointEnabled

Microsoft.Online.SharePoint.Client.Tenant

public method Microsoft.Online.SharePoint.TenantAdministration.Tenant.GetSitePropertiesFromSharePointByFilters
public property Microsoft.Online.SharePoint.TenantAdministration.Tenant.ODBMembersCanShare
public property Microsoft.Online.SharePoint.TenantManagement.Office365Tenant.ODBMembersCanShare

“Sharing is caring”

Vesa Juvonen, Senior Program Manager, OneDrive-SharePoint Engineering, Microsoft - 29th of September 2016

Better Together: SharePoint and Microsoft Graph API Beta now available!

Thu, 29 Sep 2016 16:34:00 GMT

SharePoint is home to many of the critical documents, items, and sites for organizations of all sizes. Our growing Microsoft Graph API set is designed to make working with your data, hosted across Microsoft products, as easy as possible. In this light, it’s natural that combining these two capabilities together would, we think, create something amazing.

We’re working to do just that, and are pleased to announce the Beta of SharePoint Sites and Lists APIs in Microsoft Graph. This is Beta is an early preview, and not all functionality may be present yet, but a number of new scenarios are accessible in Microsoft Graph. With these new APIs, developers can work with the set of SharePoint sites that are relevant to users and organizations. They can access and update list items that provide metadata for documents. They can connect to respective Drives for these libraries as well, providing a path towards accessing any document in an organization. These Microsoft Graph APIs make all of the important data in SharePoint available in a more flexible and streamlined manner to developers.

If you’re a regular reader of this blog, then Microsoft Graph may require no introduction, but it’s worthwhile to emphasize the many benefits of Microsoft Graph:

Consistent and unified. Microsoft Graph provides a consistent and interlinked API for working with a wide variety of types of data across Microsoft services. Developers can traverse their organizational hierarchy, discover tasks and groups associated with those users, and use organizational insights to find active working relationships between teams.
Available on devices and services. Microsoft Graph has a growing set of SDKs for devices and for services – so whether you’re working on Android apps, creating a .net Azure web site, or building a Ruby service, you can quickly incorporate Graph data into your application.
Growing support for Hybrid and On-Premises. Increasingly, Microsoft Graph will offer support hybrid deployments, meaning that organizations can flexibly expose on-premises and cloud services behind one consistent endpoint.

The consistent, unified APIs and SDKs of Microsoft Graph now come to SharePoint sites and lists. You can get started with SharePoint sites and list APIs by reading the documentation, available at http://graph.microsoft.io/en-us/docs/api-reference/beta/resources/sharepoint. We always value your feedback, but we’re especially eager to see it while we finish SharePoint sites and list APIs. Please reach out via the SharePoint UserVoice with your suggestions, and if you have questions and feedback, please use the SharePoint Technical Community or the [MicrosoftGraph] tag on Stack Overflow.

SharePoint has many other API endpoints beyond Microsoft Graph, ranging from on-server .net APIs to REST endpoints to a service-based .net and JavaScript client object model (known as CSOM). These APIs cover a very large area, including scenarios as diverse as managing the provisioning of SharePoint sites, administering the configuration of machines in a farm, or changing the metadata for a page. The CSOM and REST APIs will continue to be fully supported for the wide array of scenarios they cover.

We expect that for lists and sites, the combination of Microsoft Graph and SharePoint will make it even easier to build a wide array of applications and services that leverage data at the core of SharePoint. We look forward to seeing what gets built using these APIs. Happy coding!

Announcing the SharePoint Showcase -- now featuring web parts from the SharePoint Developer Kitchen

Wed, 28 Sep 2016 14:28:20 GMT

In the weeks since we’ve introduced the SharePoint Framework, and the months since we’ve held Developer Kitchens, we’ve seen developers create great things with the SharePoint Framework. From quick point solutions to deep SharePoint integrations, the parts we’ve seen look quite promising. We’re still in Preview, and developers are just getting started, but we’d like to take a moment to highlight the many parts already in preview and how you can get your parts featured.

Developer Kitchen Hackathon Winners

In our most recent developer kitchen in July, we embarked on a bit of a hackathon to see what our partners could build. But what’s a hackathon without friendly competition? We had a small “best part” contest, too. Judging was tough, and we’re pleased to announce the winners of the Developer Kitchen hackathon:

First Place – Groups, by Powell 365. This web part makes Office 365 Groups more discoverable within SharePoint, and offers deep contextual details on Groups.

Second Place – Document Dashboard, by Content and Code. The Document Dashboard pulls together oft-requested analytics and details about documents in your site collection. It features a number of options for customizing charts.

Third Place – Panda Poll, by Bamboo Solutions. This quick poll features easily-created questions and simple, clear charts with results.

We saw other great solutions as well – including:

Easier Excel workbook embedding from PuzzlePart
A Feed Aggregator from Sonja’s Apps
An RSS Reader from BindTuning

The SharePoint Showcase

There are many good solutions worth showing off! We created the SharePoint Showcase so that you can browse great creations from our developers. The SharePoint Showcase features detailed visuals, videos, and descriptions of these parts. Go browse the SharePoint Showcase to see our Developer Kitchen winners, and watch it grow over time as more parts are created and shared.

Because the SharePoint Framework is still in Developer Preview, the parts are not generally available to use in your sites, yet, but stay tuned for more details on how you can use parts like these when the SharePoint Framework reaches General Availability.

Keep on Building with New Contests

You may be feeling inspired to build new parts – or maybe you need a little nudge to keep going. Good news! We are launching a 3-month Hack Productivity Virtual Hackathon for anyone building SharePoint Framework parts -- as well as Office & SharePoint add-ins. We’ve got a lot of amazing prizes. Please visit http://hackproductivity.devpost.com to find out more and to register.

Even if you’re not building for the Virtual Hackathon, we would still love to see and feature what you build. Our SharePoint Showcase is open for new submissions, so if you’ve got interesting SharePoint Framework parts of your own that you plan to launch, let us know about it. Find out more about the SharePoint Showcase.

We’re starting to see the first of what we hope will be many well-crafted parts and solutions built with the SharePoint Framework. Our customers will make use of solutions like these in their sites, and developers will keep building great integrations. We all look forward to seeing what comes next!

SharePoint PnP Webcast – Using Office Graph from SharePoint Framework client-side web parts

Mon, 26 Sep 2016 10:00:00 GMT

In this PnP Web Cast we concentrated on how to use Office Graph from SharePoint Framework client-based web parts. Office Graph is intelligent grabric, which exposes personalized and contextual data of the particular user. These APIs are available through search. Office Graph information is also exposed through Microsoft Graph, but it does not require you to perform Azure AD based authorization, like with Microsoft Graph. This means that you do not need to perform additional authorization, when the provided APIs are used.

Notice. When this webcast was released, SharePoint Framework was available as a Developer Previeaw release.

Presentation covers following topics:

What's Office Graph?
Office Graph vs Microsoft Graph from authorization perspective
How Office Graph is exposed for customizations?
Available Office Graph sample client-based web parts

Web cast demo shows following details

Demo of available client-based web parts around Office Graph
How these web parts are being built?
How to access Office Graph from your client-side web parts

Web cast presenters: Waldek Mastykarz, Vesa Juvonen

Presentation used in this web cast is available from http://docs.com/OfficeDevPnP.

Video at YouTube.

Additional resources

See following resources around the SharePoint Framework.

What is SharePoint / Office DevPatterns & Practices (PnP) web cast series?

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

“Sharing is caring”

Vesa Juvonen, Senior Program Manager, SharePoint, Microsoft - 26th of September 2016

Office Dev Announcements at Ignite 2016

Mon, 26 Sep 2016 07:00:00 GMT

Over the last year, Office has gained incredible momentum, with people around the world using our apps and services in the cloud and on all devices to be more productive wherever they go. Along with this period of incredible usage growth, Office has also grown tremendously as a platform. The share of users connecting 3^rd party apps and services to Office 365, for instance, has quadrupled over the last 12 months. This is a testament to the fact that – as useful as Office is on its own – we can help people be even more productive by partnering with developers to build solutions tailored to our customers’ business needs.

At Ignite this week, we are announcing the next set of Office platform functionality, giving developers the tools they need to build even more compelling productivity applications with the Office platform. Among them you'll find new capabilities in a variety of scenarios – from traditional ones like extending Office with custom user experiences, to making your standalone apps and services smarter with the help of the Microsoft Graph, and even brand new productivity experiences powered by bots and connectors. We've compiled it all in one place for you here in this post.

As always, get started at http://dev.office.com, and watch for further updates on Twitter via @OfficeDev. Read on for lots of Office developer goodness.

Web and Device Apps: Build smarter apps by connecting to Office services through the Microsoft Graph

The Microsoft Graph is our unified API for accessing data and intelligence in the Microsoft cloud. Developers can connect to the context and insights in the Graph to make their standalone web and device applications smarter and more productive. We launched the Microsoft Graph almost a year ago, and it’s grown dramatically since then – both in terms of usage and capabilities. The Microsoft Graph is now used in tens of thousands of 1^st and 3^rd-party applications, and is used by millions of people every day. At Ignite this year, we’ve expanded the environments you can access through the Graph, added a collection of new APIs, and made it even more accessible to call from a variety of platforms through a broader set of SDKs.

One of the most important new capabilities of the Graph is support for hybrid environments. At Ignite this year, we’re launching a preview of support for Exchange 2016 hybrid environments through the Microsoft Graph. This means that developers can reach an even broader user-base with applications built on the Graph, because they can connect to mailboxes in on-premises Exchange 2016 environments connected to the cloud. It also means that customers with hybrid deployments can take advantage apps, services, and tools that target the Graph.

As well, one of the top requests for the Microsoft Graph has been access to SharePoint sites and lists. At Ignite this year we’re launching a preview enabling just that. Through the “beta” version of the Microsoft Graph, developers can now access SharePoint sites and lists, and perform create/read/update/delete operations on list items, all through a simple, purpose-designed REST interface. You won’t yet be able to perform all list-related operations through the Graph, but we’ll iterate quickly on this preview, refining the design based on your feedback and adding more and more functionality.

We recently announced the GA of the Excel REST APIs, which allow developers to interact with Excel Workbooks stored in Office 365 Groups, SharePoint or OneDrive for Business through a simple REST interface. With this capability, Excel users can create and maintain complex models using a tool they already know and love. Developers can then treat these Workbooks as purpose-built web services, that can drive the business logic or data visualization of a web or device application.

We also added a variety of other new APIs to the Microsoft Graph recently, including the GA of Outlook OpenType extensions. There are new previews of Outlook MailTips and Online meeting URL APIs as well as Azure Active Directory Dynamic Groups, Identity Protection, and Administrative Unit APIs. Check out the Microsoft Graph documentation for full details.

In addition to pulling data from the Microsoft Graph, apps can use webhooks to subscribe to notifications when data in the Microsoft Graph changes. We already support webhooks on mail, calendar, and contact entities through the Graph. This week we’re launching webhooks for files stored in OneDrive and SharePoint document libraries. Applications can use these webhooks to stay in sync with data in the Graph and respond to changes in real-time. This sort of functionality is especially important for applications that update automatically based on changes from other sources or that drive a business process in response to changes in core Office 365 data types.

We’re also showing a preview of file handlers v2 in SharePoint and OneDrive for Business. This update offers new capabilities and improved performance by connecting handlers through the Microsoft Graph. Now handlers can interact with file properties and handle actions on any file type, a collection of files, or a folder. Developers interested in getting early access to file handlers v2 and providing feedback can sign up for early access today. Keep watching dev.office.com for more details on file handlers v2 and beta availability.

Finally, we’re making it even easier to connect to the Microsoft Graph from many platforms through updates and additions to our set of Microsoft Graph SDKs. In particular, we’ve added Excel support in our generally available SDKs for .Net and Android, and we’re releasing new preview SDKs for Node.js and client JavaScript. Get the full run-down on our SDKs here.

Add-ins and Web Parts: Make your solution a native part of the modern Office

Extending Office apps with custom experiences is still one of the most popular Office extensibility scenarios. We want to make sure that you can build the same rich extensions to Office experiences in Word, Excel, PowerPoint, Outlook, and SharePoint that you could with technologies like VSTO, COM, and Full-Trust Code, but we want to do it with the best and latest web technologies, and we want it to work everywhere modern Office runs. Many of our Ignite announcements are steps toward that goal.

As part of expanding the SharePoint ecosystem, we launched a developer preview of the SharePoint Framework on 8/17. Since the launch, we've received dozens of community suggestions and issues, as well as documentation and sample contributions. Based on these, we've already released three updates to address developer feedback. We’re continuing to use community feedback to shape and drive the direction of these new platform components moving forward. For more information, check out the SharePoint hub on dev.office.com.

Office Web Add-ins enable developers of all kinds to build a wide variety of cross-platform extensions to Word, Excel, PowerPoint, and Outlook using standard web technologies. We’re now bringing the Office Web Add-in platform to OneNote as well, with the GA of add-in support for OneNote Online. We’re even using this platform ourselves to bring the popular “Meeting Details” feature of OneNote desktop to OneNote Online. Check out our getting started guide to start building your own add-ins for OneNote today.

In addition to new apps, we’re expanding the cross-platform support of Office add-ins in existing apps. Outlook for Mac now fully supports add-ins, including ribbon commands and mail compose. Add-ins taking advantage of these features on Outlook for Windows will now work on Mac with no code changes required. We’re excited to bring all that Outlook add-in goodness to Outlook for the Mac, providing a significantly expanded platform and user base for developers building Outlook add-ins.

We’re also making more Office functionality available to developers in the form of deeper Office.js API support. Word Online now fully supports the 1.1 and 1.2 requirement sets, bringing Word Online API support into parity with Word for the Windows desktop. Excel now supports 1.3 across Windows, Online, Mac, and iPad. You can read more about the new APIs we’ve added in our Office.js API reference, and you can take a look at the next set we’re working on through our open-source specs.

Finally, we want to make sure that Office Web Add-ins support seamless and flexible deployment options that match the way you want to distribute them. To that end, we’re providing an updated preview of Add-in admin deployment, which allows Office 365 tenant administrators to push add-ins to their users by username or group membership. In addition, we’re providing a preview of Add-in “deep linking”, which provides Add-in publishers with a URL that they can use in promotional materials to deep link a user into the appropriate Office application, with the given add-in installed and running. And with all these new deployment capabilities, we want to make sure that end-users understand where and how to use the add-ins they have, so we’ve added support for first-run callouts, which can teach users about newly acquired add-ins, directly within the product.

Voice, Video, Connectors, and Bots: Create the next generation of productivity experiences

At //build this year, Qi talked about an emerging new platform based on natural language and conversations augmented with custom services. At Ignite, we are making several announcements about the new types of productivity experiences you can build with Office. No user interface is as natural as natural language, and magically productive things happen when you can connect someone to another person or a service through smart conversations, bots, and agents.

Last April, we announced Connectors, which allow developers to push relevant information from their own services directly into O365 group conversations. We’ll soon launch a preview of Connectors for the inbox, bringing these same capabilities to users’ personal inboxes. This preview will be available for the following Connectors with more services to be added soon: Asana, Bing News, Bitbucket, Twitter, Trello, Wunderlist and Yammer.

We’re also announcing a preview of Actionable Messages which embed actions in both Connectors and direct email messages and help user’s complete tasks without having to leave Outlook. For example, Connector users can merge a pull request in GitHub or change the due date for a card in Trello without switching to those services.

Developers create Connector messages today by posting a JSON payload to an Office 365 webhook address and this payload has been extended to create an Actionable Message experience. By annotating actions, the message can render buttons, a dropdown list, date picker or text input box, enabling developers to model a wide variety of scenarios requiring actions.

Trello Connector card showing comment, due date, move and view actions.

Actionable Messages as direct integration within email are available in preview for apps such as SAP Fieldglass, Microsoft Flow and TINYpulse. TINYpulse Engage allows managers to send their employees a weekly pulse survey to gain feedback about workplace issues and with actionable messages, users can respond to the survey from within the context of their Outlook experience. By simplifying the process with the intuitive workflow, managers can receive better and richer feedback.

Respond to the TINYpulse survey with your choices and notes, in the convenience of your email.

Actionable Messages can help increase user engagement with your service and accelerate user productivity. If you would like to build a Connector for the inbox or use Actionable Messages, please complete this sign-up form for evaluation, as the developer platform is currently in limited preview. To learn more about building Connectors for Office 365 Groups, please see dev.outlook.com/Connectors.

Start Building!

As always, your starting point for all things Office platform related is dev.office.com. Find everything you need to get started with all of today’s announcements there. If you’re here with us at Ignite, come see detailed sessions on many of these announcements and visit us at the Office Developer booth to ask questions from Office extensibility engineers. Watch for future updates on Twitter via @OfficeDev, and provide your ideas and feedback on UserVoice.

Happy coding!

Word Online now supports Word JavaScript API requirement sets 1.1 and 1.2!

Mon, 26 Sep 2016 06:59:00 GMT

We are happy to announce that Word Online, in addition to the Windows, iOS, and MAC platforms, now supports the 1.1 and 1.2 requirement sets of the Word JavaScript API, as well as the shared Office.js API that shipped in Office 2013. If you have Word add-Ins that are currently using these requirement sets, we invite you to test them in Word Online and delight your customers with this newly supported platform!

The following is a summary of the functional areas enabled with the 1.1 and 1.2 requirement sets.

CRUD and Navigation to Word core elements:

o Paragraphs,

o Content Controls,

o Inline Picture,

o Header and Footer

o Sections

Search
Basic Range Operations

o Insert locations (before, after, start, end)

o Rich Text Formatting

o Using styles

o Document insertion

o Office Open XML R/W

o HTML R/W

o Scrolling

For more details about these APIs, see Word JavaScript API reference. See also our Word add-in code samples.

As part of this release, we are also announcing full parity with the shared API in Word Online, so you get access to bindings, custom XML parts, events, and settings.

If you’re using runtime requirement checks to see if a specific requirement is supported, note that the following requirement sets now return true in Word Online:

Updated APIs

The following table lists the APIs now supported in Word Online.

Binding APIs

(JavaScript API for Office)

CustomXML APIs

(JavaScript API for Office)

Word JavaScript

APIs 1.1 and 1.2

· Binding

· Bindings

· TextBinding

· CustomXMLPrefixMappings

· Body

· BreakType

· ContentControl

· ContentControlCollection

· Document

· Error

· Font

· InlinePicture

· InlinePictureCollection

· LoadOption

· Paragraph

· ParagraphCollection

· Range

· RequestContext

· SearchOptions

· SearchResultCollection

· Section

· SectionCollection

Questions or feedback? You can contact us via the Issues tab in the OfficeDev/office-js-docs repo.

If you want to know what’s coming next please make sure to go to our open spec repository and give us feedback on the APIs we are planning to ship next!

Vote for Office App Awards - People’s Choice!

Sun, 25 Sep 2016 07:05:00 GMT

The Office App Awards contest has now CLOSED. Congratulations to our winners!

To view the winning apps, please visit. www.betterwith.office.com/OfficeAppAwards2016

A full list will be available on this site soon.

Who is eligible for the People’s Choice Award?

Finalists were determined from nominations submitted to the contest earlier. Voting is now open.

When will the results be announced?

At breakout session BRK1019 – Vote and Celebrate at the Microsoft Office App Awards, Thursday, September 29^th - 4:15PM-5:30PM

Results will be published at dev.office.com/app-awards

These are the Candidates! You are encouraged to take a look at these in the Office Store and try these solutions.

Document Designer

Design brand and legal compliant documents and templates for organizational use.

Click here to see Document Designer in the Office Store

iWRITER 365 - Templates for Word

With just one product, use, design, manage and share all your company templates.

Click here to see iWriter in the Office Store

LawToolBox365 Court Deadline for Outlook

All-in-one court rules provider and deadline management system provider that offers deadline solutions used by law firms.

Click here to see LawToolBox365 in the Office Store

LMS365 | Assignments & Gradebook

Assignments & Gradebook Add-in enables you to create assignments and assign them to your course site.

Click here to see LMS365 | Assignments and Gradebook in the Office Store

Lucidchart Diagrams for PowerPoint

Insert interactive diagrams and dynamic wireframes directly into your presentations.

Click here to see LucidChart in the Office Store

Nintex Workflow for Office 365

Easy to use designer that helps you build workflows with advanced logic and cloud integration.

Click here to see Nintex Workflow for Office 365

Qorus DocGeneration

Adds document generation and automation features which span SharePoint and Word to provide a seamless and familiar end-user experience.

Click here to see Qorus DocGeneration in the Office Store

Saketa Kanban Board

Tool for such activities that many project management tools have incorporated a Kanban board view for their cards, activities, and tasks.

Click here to see Saketa Kanban Board in the Office Store

Smartsheet for Outlook

Coordinate any type of work and collaborate on it in real time right from your inbox.

Click here to see Smartsheet in the Office Store

Office 365 Public CDN Developer Preview Release

Thu, 22 Sep 2016 11:44:00 GMT

We are happy to announce availability of Office 365 Public Content Delivery Network (CDN) capability in the Office 365. This capability will enable you to automatically host static assets, like images and JavaScript files in CDN for providing better performance with SharePoint pages. CDN will work effectively as a geo-distributed caching proxy, by caching the static assets closer to the browsers requesting them.

Office 365 Public CDN is now released as a Developer Preview for all tenants in Office 365. You can start using it by explicitly enabling the capability on the tenant level using PowerShell cmdlets.

Following picture clarifies the logical flow of using Office 365 Public CDN.

Administrator enables Office 365 Public CDN for the tenant using SharePoint Online Management Shell.
- Cmdlets allow to designate certain SharePoint document libraries or folders to serve as a CDN origin. Note, that assets exposed via Public CDN are accessible by everyone anonymously. Therefore, resources that are considered sensitive by the company should never be placed in those libraries.
- Cmdlets also provide capability to choose the file types exposed via CDN. By default, common design asset types are enabled.
Static assets to be shared via CDN are being uploaded to the SharePoint libraries or folders, which are enabled as the CDN origins.
Assets are being exposed from the configured libraries of folders and they can be accessed using the CDN URLs.
URLs pointing to CDN location are available to be used in the SharePoint sites and in the customizations hosted from SharePoint.

In case the asset is updated in the SharePoint library, the new version will become available via CDN within 15 minutes.

> Notice. During developer preview, you will need to explicitly update the URL of shared assets in the pages and in the customizations to match CDN URL addresses. We are however working on doing this automatically with updated version, which is planned to be available later this calendar year before full worldwide release.

Video on using Office 365 Public CDN

Following videos shows in practice the steps to get started with the Office 365 Public CDN.

You can also access the video from SharePoint Patterns and Practices video channel at http://aka.ms/SPPnP-Videos.

Using Office 365 Public CDN in SharePoint Online

Here are the steps to get started with the Office 365 Public CDN.

Make sure that you are using latest version of the SharePoint Online Management Shell.
- You can download SharePoint Online Management Shell from following link - https://www.microsoft.com/en-us/download/details.aspx?id=35588
Connect to your SharePoint Online tenant within PowerShell session


$creds = Get-Credential
Connect-SPOService -Url https://contoso-admin.sharepoint.com/ -Credential $creds

Get status of the CDN settings from tenant level


Get-SPOTenant
…
PublicCdnEnabled : False
PublicCdnAllowedFileTypes : CSS,EOT,GIF,ICO,JPEG,JPG,JS,MAP,PNG,SVG,TTF,WOFF
PublicCdnOrigins : {}

Enable Public CDN in the tenant


Set-SPOTenant -PublicCdnEnabled $true

Configure allowed file extensions (optional)
- The default list is pre-populated. An admin can override it if they want to modify the file types which are shared


Set-SPOTenant -PublicCdnAllowedFileTypes "CSS,EOT,GIF,ICO,JPEG,JPG,JS,MAP,PNG,SVG,TTF,WOFF,TXT"

Add CDN origin
- Note that the origin URL must point to a document library or to a folder within. Any assets under the enabled location, including sub-folders, will be accessible anonymously via CDN.


New-SPOPublicCdnOrigin -Url "https://contoso.sharepoint.com/siteassets/folder1"

See the list of CDN origins


Get-SPOPublicCdnOrigins
 
Id Url
-- ---
1937006161eeae8fe… HTTPS://CONTOSO.SHAREPOINT.COM/SITEASSETS/FOLDER1

Remove CDN origin
- You can use Remove-SPOPublicCdnOrigin cmdlet for removing CDN locations based on the location identity


Remove-SPOPublicCdnOrigin -Identity 1937006161eeae8fe7159…

> Notice. It can take up to 15 minutes for the configuration changes to get reflected.

Usage in SharePoint pages and customizations

During developer preview of this capability, you’ll need to explicitly update the used asset links and replace them with CDN URLs. The CDN URL can be easily constructed for all the assets in the enabled library of folder, you will need to use the REST API for getting prefix for one of the assets in library/folder and use that as the constant for other assets.

The structure of CDN URL is following.


https://publiccdn.sharepointonline.com/<tenant host name>/<ID of the public CDN origin>/<sub-path under the origin>

REST API to get public CDN URL for the static asset
- The original URL will be returned if asset does not belong in any of the CDN enabled libraries, or file type is not enabled to be exposed via CDN.
- Notice. You can’t use a browser tab to test the URL returned by this API, due to the referer limitations in the CDN. You can set this URL to an asset hosted in SharePoint to validate the URL and that everything works properly


https://contoso.sharepoint.com/ _vti_bin/publiccdn.ashx/url?itemurl=https://contoso.sharepoint.com/siteassets/folder1/folder2/image.jpg
> Output: https://publiccdn.sharepointonline.com/contoso.sharepoint.com/1937006161eeae8fe.../folder2/image.jpg

Image rendition support for images from the CDN can be enabled with height and widht query parameters in the URL
- Note. both height and width parameters are required for the renditions to work
- You can also control the cropMode for the images with cropMode query parameter with following options: fit, fill, top and bottom (fit is default value).
You can use renditions with query parameters for the image URL

 
https://publiccdn.sharepointonline.com/contoso.sharepoint.com/1937006161eeae8fe.../image.png?height=100&width=100&cropMode=fit

Frequently asked questions

Is there a cost associated on the CDN usage?

No. This CDN capability is included as a standard service as part of your Office 365 subscription at least during the developer preview with no additional costs involved. We are evaluating the future options based on usage models.

Can I use this CDN from outside of SharePoint Online?

No. There is referrer limitation on the CDN URL requests. You can only reference assets from the CDN URLs when request is coming from the SharePoint Online.

How to validate CDN URL in Fiddler?

You can perform CDN URL validation in Fiddler if you include correct referrer header for your request.


Add header “Referer: https://contoso.sharepoint.com” to the GET request

Is the content published to CDN secured?

Content published through the Public CDN is available to everyone anonymously. We are considering providing additional options for secure content with following releases.

Once the assets are published to the library, how soon can they be accessed via CDN?

New assets added to the library can be retrieved using CDN URL immediately. However, if the assets are updated, it can take up to 15 minutes for the new version to be available via CDN URLs.

If I update my assets in the SharePoint site, will they automatically be refreshed in CDN?

Yes. You changes will be automatically reflected with the CDN URLs.

Can I manually construct the URL for the static assets?

The prefix is shared for all the items in the library / folder, so you can easily reuse the prefix cross all assets stored in same library / folder after getting the initial URL using the REST API to get public CDN URL for the first static asset.


https://publiccdn.sharepointonline.com/<tenant host name>/<ID of the public CDN origin>/<sub-path under the origin>

Questions or feedback

Please do provide us feedback on the developer preview in the SharePoint Developer space under Microsoft Tech Community. You can use this same forum also for any question around the provided capability.

“Sharing is caring”

Vesa Juvonen, Senior Program Manager, SharePoint, Microsoft - 22nd of September 2016

Supporting query parameters without $ prefixes in Microsoft Graph

Thu, 22 Sep 2016 10:10:00 GMT

One of the top feature requests we have heard from developers using Microsoft APIs is their preference to not use the ‘$’ prefix in query parameters. We listened and today we are announcing that starting with the /beta endpoint and soon moving into /v1.0 for Microsoft Graph, the ‘$’ prefix in the following query parameters is now optional:

select
expand (including nested expressions)
orderby
filter
top
skip
skiptoken
count
search
format

Here is an example of a simple query with Microsoft Graph using query parameters without ‘$’ prefixes:

GET https://graph.microsoft.com/beta/me/messages?select=sender,subject&expand=attachments&orderby=receivedDateTime%20desc&filter=isRead%20eq%20false&top=100&skip=0&count=true

With this new support, the query above yields the same result as this one using the ‘$’ prefixes:

GET https://graph.microsoft.com/beta/me/messages?$select=sender,subject&$expand=attachments&$orderby=receivedDateTime%20desc&$filter=isRead%20eq%20false&$top=100&$skip=0&$count=true

Here is another example of a complex query using query parameters without ‘$’ prefixes in nested form:

GET https://graph.microsoft.com/beta/me/messages?expand=attachments(select=name,size)

Which yields the same result as:

GET https://graph.microsoft.com/beta/me/messages?$expand=attachments($select=name,size)

One thing to note is that the same query parameter with and without ‘$’ prefix cannot be presented together at the top level in a query because they are now equivalent query parameters. The following is an example of a bad query:

GET https://graph.microsoft.com/beta/me/messages?$select=sender&select=subject

This query results in a 400 bad request.

You should continue to use the ‘$’ prefix when the query parameter is in a path segment. For example, here is a request that uses count to get the number of messages:

GET https://graph.microsoft.com/beta/me/messages/$count returns 200

That request succeeds but the following request which excludes the ‘$’ prefix fails because count is considered a path segment rather that a query parameter:

GET https://graph.microsoft.com/beta/me/messages/count returns 400

We hope you enjoy the option to use query parameters without ‘$’ prefixes in your future queries on Microsoft Graph.

Charlie and the team.

Bulk UPA Custom Profile Properties Update API available worldwide

Mon, 19 Sep 2016 22:22:00 GMT

We are happy to announce worldwide availability of the Bulk UPA Custom Profile Properties Update API cross all SharePoint Online tenants. This API has been in developer preview and available in first release tenants for a while, but has been now enabled cross other tenants as well. The API provides an easy way to bulk update user profile properties in SharePoint Online. Typical example use cases the following:

Synchronize Line-of-Business system profile information to SharePoint Online. An example usage would be to expose it to Search or consume the properties via customizations
Migrating to SharePoint Online from on-premises with custom profile properties

The API works in a way that you provide the needed user profile updates for numerous profiles, using a file, which is then processed by SharePoint as one asynchronous process. You can find the exact usage details from following blog post, which was released when this API was introduced for preview usage.

Introducing Bulk UPA Custom Profile Properties Update API

Here's the previously released demo on the API usage from Channel 9.

Resources

Here are existing resources for this API.

Introducing Bulk UPA Custom Profile Properties Update API - With additional documentation and implementation details
SharePoint PnP Demo - Introducing Buil API Custom Profile Properties API - Demo with managed code and PowerShell
SharePoint PnP Webcast - Introduction to Builk UPA Custom Profile Properties Update API
User Profile Bath Update API (UserProfile.BatchUpdate.API) - Code sample demonstrated in videos

If you have any questions around the released capability, please let us know in the SharePoint Developer space under Microsoft Tech Community.

“Sharing is caring”

Vesa Juvonen, Senior Program Manager, SharePoint, Microsoft - 19th of September 2016

SharePoint PnP Webcast – Introduction to PnP Partner Pack v2

Mon, 19 Sep 2016 10:00:00 GMT

In this PnP Web Cast we concentrated on covering all the key capabilities in new PnP Partner Pack v2.0 release. PnP Partner Pack is great open source reference solution, which combines multiple different PnP initiative patterns for providing polished UIs for self-service site provisioning capability. It provides end user capabilities for the site collection and sub site creation. It also provides multiple different enterprise governance solutions to manage your SharePoint Online sites easily from provided UIs. PnP Partner Pack can be used as such in your deployments or you can use it as an inspiration around what you want to accomplish.

What's PnP Partner Pack?

Ready to use reference solution for Office 365 and SharePoint Online
Open source project in the GitHub under PnP initiative
Demonstrates usage of PnP guidance and patterns in enterprise solution
Uses Office UI Fabric to provide consistent UI with modern SharePoint experiences
Concentrates on site provisioning scenarios for site collections and sub sites - Includes save site as a template replacement with remote provisioning model
Based on community effort - from the community, for the community
Easy to setup, configure and maintain
For the site provisioning handling, PnP Partner Pack uses the PnP Provisioning Engine, which can be used with any managed code solution or with PnP PowerShell, if you prefer these operations to be more admin driven

Presentation covers following topics:

What's PnP Partner Pack v2.0
Main capabilities
Requirements
Architectural Pillars
Logical process
Deployment setps
Extensibiklity Points

Web cast demo shows following details (9:10-)

Where to find PnP Partner Pack - Resources, guidance and instructions
How does the PnP Partner Pack work - what's included
How responsive experience included in PnP Partner Pack works
How you can save sites as remote templates to template level
How to provision site collections or sites using saved templates
How upcoming PnP Provisioning Template Gallery works with PnP Partner Pack v2.0
How to control centrally template updates or tenant level branding using provided UIs in the solution

Web cast presenters: Paolo Pialorsi, Vesa Juvonen

Presentation used in this web cast is available from http://aka.ms/SPPnP-Docs.

Video at YouTube.

Additional resources

See following resources around the SharePoint Framework.

PnP Partner Pack in GitHub
PnP PowerShell - If you prefer using template model with PowerShell scripts
Office UI Fabric - Used in the UIs of the PnP Partner Pack
PnP Provisioning Engine - Introducing PnP file type for template handling
PnP Webcast - SharePoint Framework vs Remote Provisioning - Why you do NOT want to use feature framework for prosioning assets
PnP Core Component - Site Provisioning Framework - Details on PnP Provisioning Engine usage
PnP Core Component - Timer Job Framework - Used also in PnP Partner Pack for backend operations

What is SharePoint / Office DevPatterns & Practices (PnP) web cast series?

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

“Sharing is caring”

Vesa Juvonen, Senior Program Manager, SharePoint, Microsoft - 19th of September 2016

Property Management Code Sample Updates Ship!

Wed, 14 Sep 2016 01:17:30 GMT

We are happy to announce we have shipped another update to the Property Management Code Sample in the OfficeDev repository on Github.com. We’ve had a lot of success with previous versions of this code sample and it is one of the most downloaded samples we have. The Property Management Code Sample demonstrates how to create a line of business system with Office 365 and mobile technologies.

The code sample includes a web application built on ASP.NET MVC5, mobile applications built with iOS, Android, Xamarin, and Cordova, and an Office Add-in for Outlook built with ASP.NET MVC 5.

The Property Manager web application demonstrates many different patterns used in real world scenarios. At a high level, the Property Manager web application does the following things.

Provisions the SharePoint Site Collection used by the Property Management web and mobile applications
Provisions information architecture and supporting components into the new Site Collection
Provisions content into the new Site Collection
Provisions Azure Active Directory groups and users
Assigns Office 365 licenses to Azure Active Directory users
Provisions Office 365 Groups
Adds Azure Active Directory users to Office 365 Groups
Provisions videos to the Office 365 Video Portal
Serves as a line of business application

The iOS, Android, Cordova, and Xamarin mobile apps demonstrate many different patterns used in real world scenarios. At a high level, the mobile apps do the following things.

Provide property inspectors and repair people information about properties they are scheduled to inspect and repair.
Allow property inspectors and repair people to submit photos and comments about inspections, incidents, and repairs.

The Office Add-in for Outlook and Outlook Web Access displays data from Office 365 SharePoint lists.

See it in action and get trained how to build it!

Check out the Training page in the Property Management Code Sample repository on GitHub to see the code sample in action and watch deep dive technical videos created by Todd Baginski to learn how solution was developed.

You can also watch the Build Smarter Apps by Connecting to Office Services session from Build 2016 that showcases many of the updates that we just added to the sample.

Microsoft Graph API Updates & Planner Service

In the last two round of updates, we updated the Property Manager Code Sample to work with Microsoft Graph v1. We also enhanced the Property Manager Code Sample to use new functionality in the Microsoft Graph including the ability to create, read and update tasks in the Plans for an Office 365 Group associated with a property/incident.

Here you can see the tasks displayed in the web app.

And here’s what the tasks look like in the out-of-the-box Planner page in Office 365.

Excel REST APIs

In this update we also incorporated the ability to return data and charts from Excel documents stored in the OneDrive associated with an Office 365 Group. The new Excel REST APIS provide this functionality. See this in action and a deep dive describing how it works in the Build Smarter Apps by Connecting to Office Services session from Build 2016.

Find Meeting Times & People APIs

This update also adds the ability to find users in Azure Active Directory with auto-complete functionality. The Microsoft Graph People API provides this functionality.

We also upgraded how to find available meeting times on a user’s calendar. The Find Meeting Times API provides this functionality.

See this in action and a deep dive describing how it works in the Build Smarter Apps by Connecting to Office Services session from Build 2016.

WebHooks & Listener Notifications

This update also includes adding WebHooks to the sample. Popup messages are displayed throughout the code sample whenever an email is sent to the dispatcher account. The sample automatically registers WebHook subscriptions and allows you to manage them as well.

Office UI Fabric Components

We also incorporated Office UI Fabric components into the web application. We created persona cards for people in the members list and bound the persona cards to data obtained via the Microsoft Graph.

OneDrive Files Thumbnails

We also created and pop out cards for files in the OneDrive lists. The pop out cards showcase the new file thumbnail capabilities. Here you can see a thumbnail for a .jpg image.

Here you can see a thumbnail for a Word document.

Mobile Apps, Visual Studio, User Interface, Installation

Our work also includes updates to all of the mobile apps to use Microsoft Graph v1.0. Other updates include updating the web application to work with Visual Studio 2015, fine-tuning the user interface of the web app and mobile apps, streamlining the installation process by automatically provisioning several components that previously were not able to be provisioned automatically, and updating all screenshots, .md installation instruction files, and the code sample walk through slide deck.

Finally, we fixed the issue where installation could fail in certain versions of Internet Explorer and we refactored the provisioning code to make it easier to understand, simpler, and quicker by running on separate threads.

In the Office Developer Podcast episode 87, Jeremy Thake, Richard DiZerega and Todd Baginski discuss the changes to the property manager web app and what it is like to build applications on the Office 365 platform. Check it out to learn more about this great sample.

This cutting edge code sample continues to evolve and demonstrate the latest and greatest Office 365 technologies. So what are you waiting for? Check out the Property Manager Code Sample today!

We work hard to provide as many code samples as possible to help you develop your own apps. Please check http://dev.office.com/code-samples for more!

OneDrive Webhooks and Large Uploads with Microsoft Graph

Tue, 13 Sep 2016 16:00:15 GMT

This week we're happy to announce two new Microsoft Graph features for OneDrive files: webhook notifications and large file uploads. This functionality is available on the Microsoft Graph beta endpoint, https://graph.microsoft.com/beta.

Webhook Notifications

By creating a subscription on a drive's root item, your app will receive a webhook notification whenever files within that drive are created, deleted, or modified. To create a subscription, your app needs to specify the Files.ReadWrite permission scope and request a subscription type of 'updated'. We’ve included an example create request, response, and notification below. Make sure to visit our documentation for more details on using webhooks with the Microsoft Graph.

Subscription Create Request

To create a new Webhook notification subscription, your application sends a POST request to the subscriptions collection:

POST https://graph.microsoft.com/beta/subscriptions

Content-Type: application/json

{

"changeType": "updated",

"notificationUrl": "https://webhookapp12345.azurewebsites.net/api/notifications",

"clientState": "My client state",

"resource": "me/drive/root",

"expirationDateTime": "2016-08-26T23:08:37Z"

}

Note: In the subscription create request it is important to use the “updated” change type as it is the only supported type for the drive resource.

Subscription Create Response

HTTP/1.1 200 OK

Content-Type: application/json

{

"id": "aa269f87-2a92-4cff-a43e-2771878c3727",

"resource": "me/drive/root",

"changeType": "updated",

"clientState": "My client state",

"notificationUrl": "https://webhookapp12345.azurewebsites.net/api/notifications",

"expirationDateTime": "2016-08-26T23:08:37Z"

}

Your app should track the resulting subscription ID and the user who subscribed, so that when a notification is received you can connect the notification to the user/drive to request the changes to the drive.

Notification

When a notification is triggered, the Graph API will POST a request to your registered notification URL, similar to the following:

POST https://webhookapp12345.azurewebsites.net/api/notification

Content-Type: application/json

{

"subscriptionId": "aa269f87-2a92-4cff-a43e-2771878c3727",

"clientState": "My client state",

"changeType": "updated",

"resource": "me/drive/root",

"subscriptionExpirationDateTime": "2016-08-26T23:08:37.00+00:00",

"resourceData": null

}

As you can see in the notification example, the resource data returned is null - you will need to use the delta functionality (/me/drive/root/delta) on the target drive’s root object to track state and find what changed. This ensures that a dropped notification does not result in any loss of state.

Large File Uploads

This week we’re also adding the createUploadSession method to driveItem. This allows your application to request an upload session which allows uploading files larger than 4 MB through Graph API. To upload larger files, your application POSTs a request to createUploadSession to create a new upload session for a file.

POST https://graph.microsoft.com/beta/me/drive/root:/file.mp4:/createUploadSession

This returns a URL which your application can use to upload the contents of the file.

{

"uploadUrl": "https://contoso.sharepoint.com/_api/v2.0/uploadsessions123191",

"expirationDateTime": "20160916T21:00:12Z"

}

Next your app logically breaks the file into fragments, each of which must be a multiple of 320KiB. For example, you could choose a fragment size of 4,259,840 bytes (approximately 4 MB) for good performance. Then, your application sequentially makes a PUT request to the uploadUrl and writes the uploads the contents of the next fragment. Your app must use the Content-Range header to specify which part of the file you are uploading, and must upload the file’s contents sequentially.

If the upload of one part of the file is unable to complete (say the connection is dropped), your app can resume the upload by remembering the uploadUrl. Your app can query for the current status of the upload URL by performing a GET request on the uploadUrl, which will return the expirationDateTime and nextExpectedRanges values, which indicate which parts of the file should be uploaded next.

When the last part of the file is uploaded, the session is committed and the file appears inside the user’s drive.

We’re excited to be rolling out this functionality to make it easier to use Microsoft Graph API for all scenarios where your app interacts with OneDrive content. Happy coding!

Ryan Gregg, Principal Program Manager, OneDrive/SharePoint and Matt Geimer, Program Manager II, Microsoft Graph

The OneNote Web Clipper Goes Open-Source

Mon, 12 Sep 2016 15:48:00 GMT

The OneNote Web Clipper is an extension for all major browsers that allows you to capture content from the web directly into OneNote. The past few months have seen many highly-requested feature updates for the Web Clipper, and this week, we're pleased to announce the open-sourcing of the OneNote Web Clipper under the MIT License.

GitHub: https://github.com/OneNoteDev/WebClipper

The Web Clipper has undergone many changes since its first inception more than two years ago, and the team wrote a post detailing everything that has been happening behind-the-scenes. Be sure to read all about it here:

https://blogs.msdn.microsoft.com/onenotedev/2016/08/31/the-web-clipper-goes-open-source/

SharePoint PnP Webcast – Referencing external JavaScript libraries from client-side web part

Mon, 12 Sep 2016 10:00:00 GMT

In this PnP Web Cast we concentrated on showing how to get use external JavaScript libraries in your SharePoint Framework client-side web parts. SharePoint Framework provides easy way to build client-side web parts, which reference external libraries, like React, Angular or for example Knockout. There are few considerations which should be taken into account, when you reference external libraries, which directly impacts the overall size of your customizations. This webcast shows how to reference external libraries and also covers different optios and considerations to optimize your customizations.

Notice. When this webcast was released, SharePoint Framework was available as a Developer Preview release.

Presentation covers following topics:

How to reference external libraries in client-side web parts
Considerations and options when external libraries are being referenced

Web cast demo shows following details

How to reference external library to your client-side web part
Needed configuration for your config.json with the external references
Bundling options for your customization
Development vs production time options

Web cast presenters: Waldek Mastykarz, Vesa Juvonen

Presentation used in this web cast is available from http://docs.com/OfficeDevPnP.

Video at YouTube.

Additional resources

See following resources around the SharePoint Framework.

What is SharePoint / Office DevPatterns & Practices (PnP) web cast series?

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

“Sharing is caring”

Vesa Juvonen, Senior Program Manager, SharePoint, Microsoft - 12th of September 2016

SharePoint / Office Dev Patterns & Practices – September 2016 release

Mon, 12 Sep 2016 08:03:00 GMT

Office 365 and SharePoint Patterns and Practices (PnP) September 2016 release is out with new contributions from community for the community. This post contains all the details related on what was included with the release and what else has been happening in the PnP world during the past month.

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

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 our GitHub projects under 'dev' branch and each month there will be a master merge (monthly release) with more comprehensive testing and communications.

This is work done by the community for the community without any actual full time team members. 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 program is 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 program, there’s no SLAs for the support what we provide from program. You can use SharePoint Developer group in the Microsoft Tech Community for providing input and to ask any questions around the existing materials. If you are interested on getting more closely involved, please check the following guidance from our GitHub wiki or a referenced PnP Webcast.

Some key statistics around PnP program from September 2016 release

GitHub repository forks at different repositories
- PnP main repository - 1759
- PnP Sites Core - 262
- PnP PowerShell - 193
- PnP JS Core - 66
Yammer group members - 4695
Unique visitors during past 2 weeks cross PnP repositories - 11326
Unique visitors during past 2 weeks in SharePoint organization repositories - 3857
Merged pull requests cross PnP repositories (cumulative) - 2295
Closed issues and enhancements ideas cross PnP repositories (cumulative) - 815
PnP Core component NuGet package downloads - 45845
Unique visitors in PnP MSDN pages during August 2016 - 29438

Main resources around PnP program

PnP under dev.office.com – http://aka.ms/SPPnP- One location for all the resources and news around PnP
PnP GitHub - http://aka.ms/SPPnP-GitHub - main repository
PnP MSDN pages - http://aka.ms/SPPnP-MSDN
PnP Community Discussions - http://aka.ms/SPPnP-Community
PnP Videos at YouTube - http://aka.ms/SPPnP-Videos
PnP training package (videos in Channel 9) - http://aka.ms/OfficeDevPnPTraining
Presentations at docs.com - http://aka.ms/SPPnP-Docs

September 2016 monthly community call

Agenda for the Tuesday 13th of September community call at 8 AM PDT / 5 PM CET:

Summary on the September 2016 release and other program updates - Vesa Juvonen ~20-25 min
What's new in PnP Partner Pack v2.0 - Paolo Pialorsi (Piasys.com) ~10-15 min
Demo on new PnP Starter Intranet for SharePoint Online solution - Franck Cornu (CGI) ~10-15 min
Demo on new SharePoint.React.SupportTicket sample - Brian Michely (Microsoft) ~10-15 min

If you have any questions, comments or feedback, please participate in our discussions in the new Microsoft Tech Community under SharePoint developer group. Notice that since Yammer Office 365 network will be shut down on 15th of September, would recommend moving the questions and discussions to new Microsoft Tech Community, so that we can continue the lively discussion around the PnP initiative as well.

PnP Office Hours

PnP Office Hours are bi-weekly calls where we talk about different topics around SharePoint engineering side and what's under development with PnP core team. These calls have also free Q&A section, if you have any questions around SharePoint development in on-premises or in cloud. Need to get recommendation to your design or having hard time with some APIs? - Drop by and we'll help you.

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

http://aka.ms/SPPnP-OfficeHours

All PnP Office Hours are being recorded and are available for view from PnP YouTube Channel. Here's the latest office hour recordings.

Notice. Next Office Hours will be on Wednesday 21st of September.

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

harePoint Framework and JavaScript Special Interest Group (SIG) has weekly meetings to cover latest changes in the SharePoint Framework side, from engineering perspective and to cover also latest development related on 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 on showing your code, just let us know.

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

All SPFx and JS SIG meetings are recorded, so that you can check the demos and discussions, if you cant' make the actual call. You can find the latest recordings from the PnP YouTube Channel. Here's the latest office hour recordings.

PnP Weekly Webcasts

We started new PnP Weekly Webcast series on October 2015 and have continued releasing new videos since that. All new webcasts are released in PnP YouTube Channel. Old webcasts and other demo videos are also found from the PnP Channel 9 section. Here's the new web casts released after the last monthly release.

8th of August - Integrating Angular 1.x to SharePoint Framework Client Side web part
15th of August - PnP PowerShell - Getting started with latest updates
22nd of August - Building simple SharePoint Framework Client Web Part
29th of August - Building Angular SharePoint Framework Client Web Part
5th of September - Getting started with SharePoint Webhooks
12th of September - Referencing external JavaScript libraries from your client-side web part

PnP repositories in GitHub

There are quite a few different GitHub repositories under the PnP brand since we wanted to ensure that you can easily find and reuse what's relevant for you. We do also combine multiple solutions to one repository, so that you can more easily sync and get latest changes of our released guidance and samples. In general we do recommend you to use the PnP sample search tool at dev.office.com for locating relevant material for you. This should be easier and faster than trying to locate relevant material from GitHub.

Here's the current repository structure, including short description for each of them.

PnP - Main repository for SP add-in, Microsoft Graph etc. samples
PnP-Guidance - Guidance, presentations and articles which are partly sync'd 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 - New repository for tools and scripts targeted more for IT Pro's and for on-premises for SP2013 and SP2016
PnP-Office-Addins - Office Add-in samples and models (starting)
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-OfficeAddins - Samples for the Office Add-ins development
PnP-Provisioning-Schema - PnP Provisioning engine schema repository

On top of the specific PnP repositories, PnP initiative also controls the new repositories under the SharePoint organization. PnP is owned nowadays by SharePoint engineering and we will be using PnP as the channel and forum to faciliate community work.

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 APIs

What's supportability story around PnP material?

Following statements apply cross 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 initiate for the benefit of others, have their normal day job as well
PnP is NOT a product and therefore it’s not supported through 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 to be clear with your customer / deployment owner on the support model

Latest changes

Provisioning Engine

The first version of the PnP remote provisioning engine was released with the May 2015 release. For the September 2016 release we have continued to add new supported capabilities and made significant improvements from stability perspective for both SharePoint Online and SharePoint on-premises (2013 and 2016). This list contains the main updates that have been added in the September 2016 release:

General overall quality and performance improvements for on-premises and online
Added support for IsVisible attribute for NavigationNode elements
Significant unit/integration test improvements
Updated base templates for the SPO, 2013 and 2016 - used in delta handling

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

PnP Partner Pack 2.0

We are happy to release PnP Partner Pack v2.0 with significant new capabilities for partners and customers to use in their SharePoint Online deployment. PnP Partner Pack is a starter kit for building typical SharePoint customizations using add-in model techniques. It's Azure AD based deployment, which provides centralized control on site templates and branding management, among the other things. Here's the key capabilities in the PnP Partner Pack v2.0:

Architectural changes
- Support for self-consistent Open XML .PNP template files, instead of .XML template files. Backward compatibility with already created .XML templates.
- Support for external template providers, and out of the box provider for the new SharePoint PnP Templates Gallery.
- Authorization layer to filter functionalities based on current user’s context.
New Governance tools like:
- Capability to apply company-wide branding (logo, color palette, fonts, background image, JS embedding, etc.) for sites and sites collections created, as well as for already created ones.
- Capability to refresh/update templates for sites created with the PnP Partner Pack v. 2.0 in order to support solutions lifecycle management.
- Asynchronous batch creation of site collections, based on an input XML file.
Implementation and UI changes:
- Updated to the latest release of PnP Core component and support for latest functionalities.
- Fully re-branded using Office UI Fabric styles.
- New set of MVC rendering templates supporting Office UI Fabric common components.
- New People Picker control based on Office UI Fabric and Microsoft Graph.

PnP JavaScript Core library v1.0

PnP JavaScript Core Library has moved to version 1.0.4. This is JavaScript library which will increase productivity of developers when you are developing JavaScript based customizations on top of SharePoint. Library has been released as a npm package and you can find the source code from GitHub. PnP JS Core library is being developed and coordinated by the PnP Special Interest Group for SPFx and JavaScript, which has weekly meetings around this development effort and general topics on upcoming SharePoint Framework. PnP JS Core library is developed using typical open source web stack tooling, so that it's fully aligned on the development models with SP Framework.

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

You can read more details around the v1.0.4 capabilities from following release blog post at MSDN or from GitHub wiki pages:

PnP library

Here's updates cross the PnP code sample library by the community on the code and documentation, which is great way to contribute as well.

PnP Core: Lots of re-factoring done to improve code quality and completeness:
- provisioning engine updates (see above)
- Added support to set icon for weblogin form
- Updates for timerjob framework related on app-only handling with SPO and on-premises versions
- General bug fixing, performance and quality improvements
- Updated to use latest CSOM version for SharePoint Online
- Automated documentation updated to md file
- Removal of deprecated methods (methods are 2 releases in the code after deprecation)
- Build and test automation improvements with unit test changes
- All PnP Core Nuget packages (Online, SP2013 and SP2016) updated with new version
PnP JavaScript Core: Version 1.0.4 released:
- Official v1.0.4 version released as npm package - check more details from following blog post
New sample react-officegraph which illustrates how to Office Graph with SharePoint Framework (SPFx) client-side web parts
New sample angular-ngofficeuifabric-todo which illustrates how to build SharePoint Framework (SPFx) client-side web part using Angular and ngOfficeUIFabric
New sample WebHooks.List which is a reference implemention on making use of SharePoint webhooks in your applications
New sample SharePoint.React.SupportTicket which illustrates how you can quickly build and package React forms with validation and send form data to a SharePoint list via the REST API
New sample Provisioning.PnPDeployer.Console is a console application that makes it easy to deploy artifacts to SharePoint OnPremise/Online. Based on the PnP Provisioning Engine, it wraps the engine's main functionnalities and provides a new layer responsible for handling tokens, authentication, sequences and logging.
New Solution Business.O365StarterIntranet Intranet projects shouldn’t have to reinvent the wheel every time for basic features (like navigation or multilingualism). This solution aims to provide the fundamental building blocks of a common intranet solution with SharePoint Online/Office 365 through a lightweight client side solution using the latest web stack development tools and frameworks.
New Solution SharePoint.SandBoxTool which is a command line utility you can scan, download, analyze and if possible fix the sandbox solutions in your SharePoint environment. This tool uses multi-threading to improve performance, uses app-only permissions to be able to access all sites and can deal with throttling in case that would happen.
Updated solution AspNetCore.Authentication An ASP.NET Core implementation of the TokenHelper and SharePointContext classes for use in SharePoint Apps. This library (and sample) demonstrates how to get ASP.NET Core provider-hosted apps authenticated through SharePoint. Updated to align with ASP.NET Core RTM version.
Updated solution Provisioning.VSTools to support VS2015, including numerous improvements
Updated PnP-PowerShell Commands with new CommandLets and with few fixes
- Overall quality improvements and bug fixes
- Added ClientTag based usage tracking for metrics
- Updated Set-SPOTheme to support theme reset
- Updated Set-DefaultColumnValues to support column defaults also for choice fields
- Updated Apply-ProvisionignTemplate to support in-memory templates
- Updated Add-SPOField to support associating site column to a list in sub site
- Updated Add-SPOFile with better file handling logic with different file statuses
- Updated Add-NavigationNode to fix issue with relative URLs
- Added support for latest CSOM
- Updates on the test cases
- Updated help details for CmdLets
- Updated documentation for CmdLets
Updates to the PnP Partner Pack
- As mentioned in specific chapter

PnP Guidance articles

The PnP Guidance repository contains guidance articles which are published at MSDN. Starting from end of May 2016 this process was changed to be fully automated and there's automatic contributors list in the MSDN side showing who have been providing updates to these documents. We are looking forward on your contributions around real life learnings in different areas. Read more details around this open publishing model from following blog post

Contributing to Office Dev PnP and SharePoint PnP documentation just got easier

Here's new guidance articles since the last release communications

See MSDN articles from the PnP MSDN section at http://aka.ms/OfficeDevPnPMSDN

PnP Guidance videos

You can find all PnP videos from our YouTube Channel at http://aka.ms/sppnp-vidoes. This location contains already significant amount of detailed training material, demo videos and community call recordings. Since last release communications, we have released one additional guidance video:

SharePoint Sandbox Solution Scanner

Since YouTube channel is relatively new, some of the PnP videos are also in the PnP Channel 9 video blog.

Key contributors for the September 2016 release

Here’s the list of active contributors (in alphabetical order) during past month in PnP repositories. PnP is really about building tooling together with the community for the community, so your contributions are highly valued cross the Office 365 customers, partners and obviously also at Microsoft.

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

Bill Ayers (Flow Simulation Ltd.) - @SPDoctor
Dan Beaulieu - dbeaulieu
Erwin van Hunen (Rencore) - @erwinvanhunen
Elio Struyf - @eliostruyf
Franck Cornu (CGI) - @FranckCornu
John Liu (SharePoint Gurus) - @johnnliu
Luis Mañez (ClearPeople) - @luismanez
Mauricio nunes - mauricionr
Michael Schau (WorkPoint A/S) - @SchauDK
Michael Toole (Perficient, Inc.) - miket9884
Paolo Pialorsi (PiaSys.com) - @PaoloPia
Pieter Veenstra (Triad) - @PieterVeenstra
Radi Atanassov (OneBit Software) - @RadiAtanassov
Shantha Kumar T - sksnips
Simon-Pierre Plante (SPP Technologies) - spplante
Stephan Steiger (IOZ AG) - @robi26
Thomas Berman (DQC Sverige) - thomasberman
Todd Baginski (Canviz) - @toddbaginski
Waldek Mastykarz (Rencore) - @waldekm
Wictor Wilen (Avanade) - @wictor

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 on time for this communications. If you still want your logo for this month's release, please let us know and share the logo with us. Thx.

Microsoft people: Here’s the list of Microsoft people who have been closely involved on the PnP work during last month.

Antons Mislevics (Microsoft) - antonsmislevics
Bert Jansen (Microsoft) - @O365Bert
Brian Michely (Microsoft) - @brianmichely
Chakkaradeep (Chaks) Chinnakonda Chandran (Microsoft) - @chakkaradeep
Dan Budimir (Microsoft) - MSDN blog
Frank Marasco (Microsoft) - @frank_marasco
Kiki Shuxteau (Microsoft)
Koen Zomers (Microsoft) - @koenzomers
Laura Graham (Microsoft) - Lauragra
Mike Morrison (Microsoft) - mike-morrison
Olivier Carpentier (Microosft) - @OlivierC
Patrick Rodgers (Microsoft) - @mediocrebowler
Vesa Juvonen (Microsoft) - @vesajuvonen

Latest traffic statistics

Here's traffic statistics from the PnP, PnP PowerShell, PnP Sites Core (.NET) and JavaScript Core component repositories.

Traffic at PnP repository

Traffic from PnP Sites Core repository

Traffic from PnP PowerShell repository

Traffic from PnP JavaScript Core Component repository

See About Repository Graphs for more details on above statistics.

Next steps

September 2016 monthly community call is on 13th of September at 8 AM PDT / 5 PM CET for latest release details with demos - Download invite with detailed schedule for your time zone from http://aka.ms/sppnp-call.

“Sharing is caring”

Vesa Juvonen, Senior Program Manager, SharePoint, Microsoft - 12th of September 2016