Andrew Connell’s Post

In my newsletter this week, I revisited one of the most useful and free tools SharePoint Framework developers can have on their dev environments: NVM! One challenge I see SPFx developers face time and time again is dealing with different Node versions & Node package dependency versions. One of the best decisions every SPFx developer can make is to adopt using a node version manager (NVM) to better manage their environment. Available for Windows & MacOS, NVM allows you to have multiple versions of Node.js installed and enables each to have its own global package registry. Have you run into one of these issues with your environment? ➡️ Not having administrative access to your developer environment. ➡️ Only one collection of globally installed packages. ➡️ Only one instance of Node.js can be installed at a time. Then you should check out NVM & see how it can improve your life! Miss this week's newsletter? No worries... check it out (and subscribe to get future issues delivered straight to your inbox every other Tuesday) to learn more AND get a summary of the most recent news in the Microsoft 365 development space! https://lnkd.in/errVh_fa #Microsoft365 #Microsoft365Dev #SharePointFramework #SPFx #Node #NVM

I got tagged in a GitHub issue & on Twitter/X about a #SharePointFramework issue when using #SPFx to create tabs for #MicrosoftTeams. https://lnkd.in/gmFwB9Pm https://lnkd.in/gUNR5YXC Setting aside Microsoft's guidance is pretty crappy 🗣️ "just use the Classic Teams client, not Teams v2"... Great... what happens in 6 days on July 1 when Microsoft forces everyone to use Teams v2? 🤷♂️ This is just another reason why I think SPFx is a crappy solution to create tabs for Microsoft Teams. What do you think? #Microsoft365 #Microsoft365Dev

From time to time, I see similar questions come up from students in my SharePoint Framework courses. One that’s come up a bunch recently is the first-run experience with a new project or one that you’ve recently acquired. When you run any gulp tasks, like gulp serve, you get the following error: Error: Cannot find module 'node:os', or something similar. 🧐 Root cause of the error The most likely cause of this error is that you haven’t installed the project’s dependencies or you haven’t run npm install on your project. Node.js projects, which is what a SharePoint Framework (SPFx) project is, almost never include their dependencies when we share them with others. This is a common practice among platforms that leverage package managers. In the Microsoft world, even dotnet projects are subject to the same, having to install their dependencies using the Nuget package manager. 🤔 When does this happen? Great question! This is the case when you create a brand-new project. But it also applies when you acquire a project by cloning it from a repository such as one in Azure DevOps, GitHub, or other source code repository hosters. Lacking the project’s dependencies also applies when you download the project from some other resource, such as the PnP SPFx sample repos or as one of the samples from my SharePoint Framework courses that students can access. How do you fix it? I explain this in my recent article: https://lnkd.in/eh6WMuxN #Microsoft365 #Microsoft365Dev #SharePointFramework #SPFx #Node

Miss last week's #PnP community call for #SharePointFramework developers? Every other Thursday, learn what's new in the #SPFx space for #Microsoft365Dev's. Last week they teased that the next release of SPFx will include new chart types of Adaptive Card Extensions (ACEs), building off the line chart that was introduced in SPFx v1.19. Watch the full recording of the session on YouTube: https://lnkd.in/egCEadzb

Do you 🫵 have a burning question about Microsoft 365 development topics? 🙋♀️🙋♂️ Want the latest news related to Microsoft Teams, the SharePoint Framework (SPFx), Microsoft Graph, SharePoint Embedded, or other Microsoft 365 dev topics? I'll also cover what's coming with the SharePoint Framework & look back at some of the announcements following the Microsoft Build 2024 conference I'm going live TOMORROW, THURSDAY, June 20 at 11 AM ET (4 PM GMT), for my office hours dedicated to Microsoft 365 full stack developer topics. Got a question about M365 topics like… ✅ SharePoint Framework (SPFx) ✅ Microsoft Teams development ✅ Microsoft Graph ✅ SharePoint Embedded ✅ Office Add-ins ✅ Microsoft Build 2024 announcements Join me in this AMA / office hours livestream on my YouTube channel. Use the following link to subscribe to my YouTube Channel & get notified when the livestream is about to start! Will you join me? 👉 https://lnkd.in/ecsC2nwg #microsoft365 #microsoft365dev #sharepointframework #spfx #microsoftteams #SharePoint #sharepointembedded #microsoftgraph #officeaddins

In my recent newsletter, I shared some important updates about the upcoming retirement of #SharePointFramework (#SPFx) domain-isolated web parts. This change aims to eliminate IFRAMEs in SharePoint pages, a move that could impact the security of your SPFx solutions. 🔍 What's the Issue? When an SPFx solution requests an access token from SharePoint Online (SPO) using #MicrosoftEntra ID (#AzureAD) API, SPO can't identify the app making the request. This results in permission grants applying to the entire tenant, not just a specific application. 🛡 How Domain-Isolated Web Parts Helped ✅ Custom Entra ID Application: Each SPFx solution had its own Entra ID application. ✅ Dynamic Domain: Web parts loaded in an iframe on a custom domain, ensuring permissions were granted only to specific apps. For some organizations, this was crucial. I'm familiar with a large European organization that stopped using SPFx solutions that required permissions to Microsoft Entra ID-secured endpoints such as Microsoft Graph or custom API access due to this upcoming change. Options for Hardening SPFx Solutions ✅ Validate Access Tokens: Check the token for your SPO tenant ID, the SPO app ID, and the specific user making the request. ✅ Proxy Approach: Use your own Microsoft Entra-secured endpoint as a middle-man to call #MicrosoftGraph securely where you can perform additional checks on the user accessing the endpoint. Your Thoughts? 🤔 Is this news impacting your organization? 🤔 Do you need a more secure SPFx solution? Want all the details and my recommendations? Read my recent newsletter issue on this topic here 👇 https://lnkd.in/ea8rECjw Subscribe & join thousands of your fellow #Microsoft365Dev colleagues who get insights & a summary of the latest news every other Tuesday, delivered straight to your inbox!

Hey all you 🫵 #Microsoft365Dev! As the months tick by, Microsoft is making #MicrosoftTeams the center of gravity even more for custom development in the #Microsoft365 landscape. A Microsoft Teams app is a Microsoft 365 app! Depending on what you create, it can run not just in the Microsoft Teams clients, but also in #SharePoint Online, #Outlook, the Microsoft 365 apps, and more! Want to learn more? Join me in Stockholm this December for ESPC 2024! Last year in Amsterdam, I was honored to pick up the award for “Best Online Courses”. This year, I’m talking about two things: Microsoft Teams app development & #SharePointEmbedded! Join me for a full-day pre-conference instructor-led workshop learning the “ins & outs” of creating Microsoft Teams apps. You’ll learn how to create tabs, bots, and message extensions AND how to use Teams apps to customize Copilot! But that’s not all, in my breakout session I’ll talk about a hot and exciting service from Microsoft that gives developers the ability to use SharePoint as their app’s document storage solution using SharePoint Embedded! You’ll learn what you can do, how to set it up, and how to read and write documents to your SharePoint Embedded Containers! Learn more about my full-day workshop & breakout session: https://lnkd.in/eJdJ8XRa

I had a great time catching up with Jeremy Thake on the Microsoft 365 Developer Podcast in ep312, "Copilot Extensibility Build 2024 Follow-up with Andrew Connell"! 📣 If you didn't hear, I've joined JT as his regular guest co-host once a month, firing up that podcasting mic 🎙️ energy again! In this episode, we looked back at the #Copilot (or is it lower-case "copilot"... we tackle that too!) announcements from Build and dug into some of the points that I thought needed a bit more clarification. Take a listen! https://lnkd.in/epTnn4p2 And be sure to check out the show notes to get my full Build 2024 wrap-up for everyone that's a #Microsoft365Dev, including my custom-build YouTube playlist of all the keynotes and sessions from Build 2024 that #Microsoft365 developers should be aware of.