Blog

Demo of the Microsoft Graph “Quick Start” which generates a full code project with a new App ID (Client ID). Azure Active Directory (AAD) manages a registration of application ID paired with API permission grants for which API calls can be made. From there, the client side JavaScript application can invoke HTTP GET to fetch JSON data for the allowed MS Graph API endpoints. Cheers!

Ever wondered what fixes are inside of a given CU? Please see attached PDF with full detail. I wanted a new format for easy reading. Show management and make the business case for why downtime should be taken to apply CUs. Also posted at http://sharepointupdates.com/

High performance – Faster CPU, higher RAM, and low latency network connections within the data center offer premium speed for any heavy operations. Even with a cloud remote API world, leverage those network connections bring faster execution time than any local laptop script could offer.

Long running operations – Execution of large PowerShell scripts, inventory of cloud hosting systems, can run for many hours. Having a stable location to host those scripts provides continued uptime. Laptops can disconnect wifi, sleep, or shutdown. Find a stable home for large script runs.

Debug server side code – With SharePoint Server on-premise, for example, you can access site collections locally. Having VS Code available on the server provides familiar rich debug experience for productivity on both frontend (and classic back end) development.

Share work with peers – Ability to disconnect remote desktop RDP sessions and “pass the ball” to co-workers provide higher coverage. VS Code is a great location to not just code but also execute scripts. Leaving remote desktop open with a service account gives higher staff cross training where peers can resume each other’s work seamlessly. No need to even remember folder paths, just connect and begin.

Training consistency – Same mechanics for local laptop coding can be employed on server side. No need to “flip modes” and fall back to PowerShell ISE, Notepad, or old editors.

Extensions – Productivity gains from time saving and error checking third party extensions. Not just for local laptops. Same benefits can be realized when we’re working server side too.