What did you build last week?


I am super curious!


What did you build last week in Microsoft 365?  Which problem did you solve? Where did you get stuck? What did you use? Want to share something? 


Please reply below- don't be shy =)jon-tyson-hhq1Lxtuwd8-unsplash.jpg

16 Replies
I needed something to move a lot of emails from one folder to another. Started from building a flow. Ended up using CLI for Microsoft 365 8)

@waldek sweet! So CLI is also a tool for individual productivity? 

Totally! We have several commands that focus on things that are relevant to end-users, like creating tasks, moving emails, etc. If you need to do more than one of something, CLI is a great time-saver!

@Luise Freese Fun with Power Apps and flows.  Using those two tools along with a set of SharePoint lists, you can really build complex, valuable solutions. (I know - some people say we should use Dataverse, but that's not realistic in many organizations).

@Marc Anderson as always, it depends. There are use cases for SharePoint, Dataverse and SQL, even for Excel. From a licensing perspective, Dataverse for Teams solves a lot, as its seeded in Microsoft 365 licenses. 


This is a nice post on how the decision on your backend impacts the performance of your app: Considerations for optimized performance in Power Apps | Microsoft Power Apps



@Luise Freese 


I've been trying and failing with my team to figure out getting custom connectors into SPFx web parts, so I at least made some progress - whether it's down the right path, I do not know.


In terms of actual success, thanks to the Power BI community, I figured out with an Exchange data connection how to map the duration of categorized meetings into a growth visualization, comparing month to month, after many weeks of trial and error!

Cool! Are the connectors that you’re working with in SPFx APIs that you’d like to use? Anything specific that you’re blocked with?

@waldek The use case is building a dashboard with various SPFx web apps (maybe a pre-built grid like Kendo offers) connected to the client's various services - some more custom, and some more common like Confluence.  We have been trying to build custom connectors through PowerApps with schema defined with some guidance from the glorious SharePoint Cowboy, who said they looked right.  We aren't sure about authentication, because most of them aren't going to support OAuth 2.0, which the tutorials we are finding mostly involve authenticating through Azure and OAuth. 


As the JUNIOR junior working on the SPFx side, I'm trying to figure out what I'm pulling in since we don't have it all cemented on the connector side, and how to specifically map the schema to one of those pre-built grid view lists.  It seems like on some of the examples I was looking at, the data keeps pulling from a json file that's built into the web part, and I can't figure out how that would be updated live data.

Connectors make a lot of sense if you plan to consume these APIs in Power Apps or flows. In the context of SPFx though, they don't add any value, because to use them, you'd need to build an HTTP-triggered flow that would expose the data as an API, which you already have. Instead, it would be easier to connect SPFx web parts directly to your API.

You mentioned that these APIs don't support OAuth. If this is the case, then building a proxy-API secured with AAD, which you could call from SPFx and which would relay calls to the API could help you.

@Luise FreeseI created the V2 of a SharePoint team site, including a mini knowledge base management system with metadata and document preview windows on hover and a Yammer communities catalog built with Microsoft Lists. I had to edit a lot of JSON card layout, but the result is pretty satisfying :smile:

@Feder365 this sounds awesome! If you want to learn more about JSON, you can head over here: Introduction to JSON - Microsoft Tech Community 

I recently build a document preview (dynamically) like this: 


Create a dynamic preview for documents in SharePoint – M365 Princess - How did you approach this? 

@Luise FreeseRegarding to the document preview, the solution wasn't a list nor a SharePoint page with webparts. Starting with a document library, I created an image column and used src: @thumbnail in JSON code (knowledge source here). This is the result:




@waldek I really appreciate your input - would you have a good tutorial on getting the proxy-API secured by AAD?  Part of our problem we keep running into is that it seems like all of the walkthroughs we find are doing something fundamentally different than what we are trying to accomplish, and of course we are getting different recommendations depending on who we ask without actually getting any data pulled through.

I totally understand your struggle. Like with everything unfortunately, there are multiple ways of doing things and often their effectives depends on an obscure detail.

Before I send you out to research something else, that might or might not work, what authentication model does your API support? Does it work with an API key or an app token that you need to add to every request either via query string or a header?

@waldek I greatly appreciate it!  We are working with 3 main types of APIs in this solution - one of them uses API tokens, one of them (Atlassian) says it prefers HTTP Basic and supports OAuth, but I believe it's OAuth 1 (it's on-prem), and the third is wide open because we just built it and if it gets locked down, it will be however we choose.


Last night we started looking at Azure Functions as an option since we are reaching out to everyone we can for advice, and that was one recommendation to use to take in the APIs and feed them right to SPFx.

@LindsayTShelton when looking at Azure Functions, please check out Proxies. They could offer you a lightweight way to pass requests between SharePoint Framework and your existing APIs extending them with the necessary information like API keys, tokens, etc.


When it comes to securing Azure Functions, the easiest way is by using the Authentication and Authorization settings and secure your Function with Azure AD.


SharePoint Framework has a built-in support accessing APIs secured with Azure AD.


One thing that I haven't checked, if configured proxies are subject to authentication and authorization settings. If they are, and proxies are sufficient for you to relay requests, they would be a great and robus solution that doesn't request any custom code on the API side.