This is a crazy one, and if you have read ALL my Microsoft Flow blog posts, you’ll be familiar with all these pieces. We are going to connect them a different way though, and the result is still awesome.
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.
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!
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.
The flexibility of SharePoint is empowering to users, but it’s hard to ensure compliance with policies and regulations. Companies in highly regulated industries are starting to venture into Office 365 (usually in hybrid configurations), yet many of the approaches and third-party products for compliance are locked into on-premises farm solutions. In this session, learn how to apply OfficeDev Patterns and Practices technology to add compliance features to modern and classic SharePoint Team Sites.
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.
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.
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.
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.
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.