S01E23 - Build Win32 apps Using PowerShell, VSCode Tasks & Intune Graph - (I.T)

00:00 - Intro
09:15 - VS Code Command Palette
09:53 - Build & Publish task
15:03 - Microsoft Graph name
23:55 - Tasks explained
31:12 - Creating a simple task
45:10 - Ben's Repo
45:52 - Wrapping up

Visit our websites and social media for more or to get in touch with us

Steve Hosking - Microsoft EM+S MVP

Adam Gross - Microsoft EM MVP

Ben Reader

[devinmcelheran]

The reason for the name Graph is from graph theory in mathematics. A graph is basically a collection of nodes and their relationships to each other. This makes sense in the Facebook sense where the nodes are people, pages, etc, and the relationships are friends, family, locations, liked pages and interests, etc. In Microsoft Graph the nodes are things like users, groups, applications, documents, security events, so on, and the API allows you to explore and build on the relationships between them for productivity, workflows, security, and so on.
That said, I have absolutely no idea how to develop for Graph and I think it would be very interesting for Intune.Training to demonstrate some of this.

[TheRealExbit]

Another great video and resource! I have been watching since the beginning and can't wait to use some of the concepts you displayed. I am looking forward to the AppLocker video as I have been working with Intune and MultiKiosk App mode for Digital Signage. Even though I have the correct AMUID, AppLocker seems to be blocking my electronjs framework application. Keep up the great work! Cheers!

[RaviKumar-pktq]

Hello Ben can you please share the Install.ps1 for the teamviewer, it will help us to under stand the parameters used in the script and those i will try to replicate for other application. Thank you :)

[AudiSP]

Guys, When will the Configuring AppLocker Episode 22 released again?

[christopher]

I've tried everything to get tasks to work, they simply don't work. Whether it's external tasks to command line executable's or scripts; nothing works.

[jimdruce]

Guys firstly great video series and thanks for sharing. One question which we are really struggling with, we're trying to run our environment completely Azure AD only. We've been successful in setting most of this up without any issues thanks to a lot of content which you've shared. But we've hit one basic snag which i just find a tadge bizarre that Microsoft have not considered this. If you setup users as standard accounts, this still gives them the ability to run things like regedit, powershell. and command line. We don't want users to be able run these applications and poke around albeit with read only access. Surely there is a simple way of disabling these exe's in Intune/Endpoint manager... Any thoughts on this?