Forms for Excel, new experience for Excel survey in Office 365

Forms for Excel, new experience for Excel survey in Office 365

Forms for Excel, powered by Microsoft Forms, has replaced Excel Survey. This update, available for Office 365 Commercial and Education customers, comes with a modern experience to make it simple and easy to collect information from users in the same organization, to anyone in the world. Forms for Excel includes new features such as response time, responder name, images, videos, themes, and branching logic.

Provisioning an Office 365 group with an approval flow and Azure functions

blog.atwork.at | Provisioning an Office 365 group with an approval flow and Azure functions

In real world environments, organizations usually want to restrict the group provisioning so that IT can control the wild growth of groups. This article series shows how to create an Office 365 group with an attached approval process with SharePoint Online, Flow and Azure functions. See how this works here!

Manage tenant-scoped SPFx extensions across your SharePoint sites

Manage tenant-scoped SPFx extensions across your SharePoint sites

SPFx web parts deployed at tenant scope will appear everywhere in the picker, but for SPFx extensions there is still something you need to do locally, and that’s “associate” your extension with the site/web/list/field. For Application Customizers, it’s this step which allows you to control exactly which sites use your extension.

Using SharePoint Remote Event Receivers with Azure Functions and TypeScript

Using SharePoint Remote Event Receivers with Azure Functions and TypeScript

In this tutorial I’m going to show how to set up Azure Function, which acts as http endpoint for SharePoint Remote Event Receiver, everything running on Node.js and written in TypeScript! We’ll also use pnp-js-core to interact with SharePoint REST API from event receiver.

Calling SharePoint CSOM from Azure Functions

Calling SharePoint CSOM from Azure Functions (Part 3) | Bob German’s Vantage Point

This series will show you how to call SharePoint’s Client-Side Object
Model (CSOM) from an Azure Function. It’s divided into three sections,
in hopes that the first two sections are reusable in other scenarios. I’ll probably add more scenarios in the future, but will keep the URL’s the same.

Overview of labels – Office 365

Overview of labels – Office 365

Labels in Office 365 can help you take the right actions on the right content. With labels, you can classify data across your organization for governance, and enforce retention rules based on that classification.

With labels, you can enable people in your organization to apply a label manually to content in Outlook on the web, Outlook 2010 and later, OneDrive, SharePoint, and Office 365 groups.

Apply labels to content automatically if it matches specific conditions, such as when the content contains:

  • Specific types of sensitive information. This is available for content in SharePoint and OneDrive.
  • Specific keywords that match a query you create. This is available for content in Exchange, SharePoint, OneDrive, and Office 365 groups.

Custom modern page header and footer using SharePoint Framework

Custom modern page header and footer using SharePoint Framework

The SharePoint Framework gives us a new way to deploy JavaScript-based customizations to SharePoint. These include web parts (for both classic and modern pages) and now Extensions such as Application Customizers that allow you to embed JavaScript on modern pages.

To extend the functionality of my SharePoint-hosted add-in to modern pages using the SharePoint Framework, I created a new SharePoint client-side solution containing an application customizer extension to handle the rendering of the header and footer on all modern pages, reading the same configuration values from the site property bag that are set by the add-in part from my original SharePoint-hosted add-in.

Azure Function Development-Deployment Strategy

Azure Function Development-Deployment Strategy

The goal is to be able to have a set of functions that do work against our SharePoint tenant. How they are triggered (HTTP Trigger, Timer Trigger, etc) is irrelevant, what is relevant is that I want to leverage the same Azure Application and its corresponding certificate, as well as some common code for all the functions.

Embrace the power of SPFx WebPart properties

Embrace the power of SPFx WebPart properties

Spfx Web Part properties can now have metadata, which can be indexed by search engines, and can auto-update if it is a URL and the refrecned asset is moved.

Introducing the PnP Provisioning Engine

Introducing the PnP Provisioning Engine

This short whitepaper introduces the PnP Provisioning Engine […] now days with the new CAM the approach should be based on provisioning artifacts using the so called „remote provisioning“ technique. But what does mean to do „remote provisioning“? It means using the Client Side Object Model (CSOM) to provision artifacts, instead of using the feature framework.

Well, and what if I want to model and provision artifacts using a test and a production environment? Or what if I want to automate provisioning of artifacts, just because I want to sell my customizations to multiple customers? Or again, what if I want to define a custom site template that I want to re-use across multiple site instances, like customer-oriented sites, or project-oriented sites?

Using the new PnP Provisioning Engine, you can model – even simply by using the web browser – the design of Site Columns, Content Types, List Definitions and Instances, Composed Looks, Pages (either WebPart Pages or Wiki Pages), and much more. When you are done with the design, you can export what you have done into a persistent provisioning template format (XML, JSON, or whatever you like), and you can apply that template to as many target sites as you like.