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.

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.

Running #ProjectOnline #PowerShell in #Azure using #AzureFunctions #PPM #Cloud #Flow #LogicApp Part2

Running #ProjectOnline #PowerShell in #Azure using #AzureFunctions #PPM #Cloud #Flow #LogicApp Part2

Following on from part 1 where I introduced the idea of automating certain Microsoft 365 PPM Project Online customisations using PowerShell, Microsoft Flow / Azure Logic Apps and Azure Functions, in part 2 I will set up an example automation for creating a Project Online event driven snapshot application on project published without having to set up any server or write any complied code!

Perhaps the only SharePoint Framework web part[s] you will ever need…

SharePoint Framework and the missing script and/or content editor web part. Here are three sources to learn about how you could roll your own:

Tech and me: Perhaps the only SharePoint Framework web part you will ever need

Perhaps The Only OTHER SharePoint Framework Web Part You Will Ever Need

Converting your CEWP Customizations to the SharePoint Framework

Office UI Fabric JS

Office UI Fabric JS

Simple components that focus on appearance and styling while showing the visual language of Office. Fabric JS provides you with simple components that don’t require a framework. It’s open source, easy to extend, and ready for you to add what makes your project unique.

Fabric JS works great with Add-ins and is the recommended front-end toolkit for making your next Office Add-in.

Verwenden des clientseitigen Steuerelements „Personenauswahl“ in von SharePoint gehosteten Share Point-Add-Ins

Verwenden des clientseitigen Steuerelements „Personenauswahl“ in von SharePoint gehosteten Share Point-Add-Ins

Mit dem clientseitigen Personenauswahl-Steuerelement können Benutzer schnell nach gültigen Benutzerkonten von Personen, Gruppen und Ansprüchen in ihrer Organisation suchen und diese auswählen. Bei der Auswahl handelt es sich um ein HTML- und JavaScript-Steuerelement mit browserübergreifender Unterstützung.

Shire microsoft customer modern digital intranet workspace using SharePoint and Office 365

Shire microsoft customer modern digital intranet workspace using SharePoint and Office 365

On July 13th, Microsoft held a panel webinar with their customer, Shire – a recognized leader in rare diseases, along with numerous Office 365 MVPs (full panelist list below). We got to hear how they planned, built and use their beautiful and engaging digital workspace – The Hub – to help inform and engage everyone throughout the company in a consistent, sustainable way.

The panelists highlight the importance of governance throughout the project, describe numerous business cases, and cover the use of innovations including SharePoint communication sites, leveraging the SharePoint Framework (SPFx), multi-column page support, new web parts and page capabilities – all used to create rich and compelling sites to achieve their desired outcomes.