Content relating to the Microsoft 365 Suite.
With Microsoft iminently shuttering the capability to send emails programmatically via MS Exchange in Azure, developers need to switch to a mechanism that will be supported moving forwards. Enter Microsoft Graph. This article describes how the MS Graph API can be leveraged to replace MS Exchange based mailing for the programmatic sending of emails.
Converting a file from DOCX to another format (such as PDF) had long been a pain in SharePoint and usually led to resorting to using Word Automation Services (WAS). Fortunately, modern SharePoint (Online) and the Microsoft Graph API mean you can do it with a few Web API calls.
The SharePoint Framework (SPFx) is Microsoft’s latest addition to the SharePoint development family. It is custom web-part and page extensions programming model aimed at replacing the over-used (and potentially dangerous) Script Editor Web Part (SEWP) and Content Editor Web Part (CEWP) in SharePoint Online (SPO) and recent versions of on-premise SharePoint too.
When developing SharePoint (SP) Add-ins, you will generally want to avoid having to deploy them to your SharePoint Online (SPO) tenancy’s public app catalogue until you are going to release them. Microsoft have catered for this and there is a way to enable a ‘developer’ app catalogue at site-collection level using some PowerShell commands.
Microsoft 365’s PowerApps can be created based on a fixed layout for one of a portrait mobile device (i.e. phone) or landscape device (i.e. desktop or tablet) only. Given that most users will adopt a combination of devices when accessing apps, this either means you have to develop your PowerApps app twice or you have to try to get something not designed to have a responsive layout to be responsive.