The course is part of this learning path
Publishing Applications With Microsoft Endpoint Manager looks at what's involved when publishing apps to fully managed and BYOD devices. This course examines how to publish and deploy different app types and how to use Microsoft Endpoint manager to implement application configuration and protection. We see what an app needs to support configuration and protection policies, what those policies offer in the way of data protection, and how a policy can configure an app's access to a mobile device's hardware and capabilities. While the course's primary focus is deploying apps to mobile devices through app stores, we also look at using Endpoint manager to publish a custom in-house app to a desktop client.
Learning Objectives
- Overview of app publishing scenarios
- Learn about app protection policies and how to create one
- Learn about app configuration policies and how to create one
- Publish a custom line of business to a Window client
- See how to investigate deployment issues
Intended Audience
- Students working towards the MS-101 Microsoft 365 Mobility and Security exam
- Those wanting to learn how to use Microsoft Endpoint Manager to publish and deploy applications
Prerequisites
- There are no prerequisite courses needed to take this course
Let's deploy a Windows line-of-business app from endpoint manager to a local Windows client based on a user's identity. Currently, the app isn't installed on my Windows 10 machine. To publish an app, open the Endpoint Manager portal and click apps in the left-hand menu blade. The all apps home page displays all the apps you've published, and my cupboard is looking a little bare at the moment. Click the add button to start the publishing wizard. As I said, this is a line-of-business app just for users in my domain, but we can see all the other app types, where they are sourced from, that you can publish from the Endpoint manager. I'll select line-of-business. While the app I'm publishing is a WinForms app, it is x64, not a Win32 app.
There is the opportunity to validate your application with Test Base for Microsoft 365, but hopefully, you've done the necessary testing before deploying your application. Anyway, with the app type selected, hit the select button. Add app is where we upload all the necessary package files our application needs to run. This application and the supporting files it needs have been bundled up into an MSI deployment package. As you can see, we have the name of the package, Windows is the platform it will run on, and it will be executed in the context of a user. Click OK. Under app information, I'll provide the publisher value, which is the only one that is mandatory and not already filled in. And, of course, the publisher is me. I will select an app logo, but that is for display in the company portal, not an app icon for the deployed application. The assignments page is where we determine who will have access to the application.
I have created a user group called Line of Business apps, abbreviated to lobapps, to which I belong, so we'll add that user group. With the user group added, click next. We can review our settings before hitting the create button. The application entry in the endpoint manager is relatively quick to create but uploading the deployment package takes a bit longer. The application doesn't immediately appear in my start menu, but if I log out and back in, we can see it sitting at the top of the recently added list. Going back to the All Apps home page, we can see IntuneLOBDeploy is sitting there as a windows MSI line of business application that has been assigned. Clicking on the line and drilling into the app, we can see it has a pending install status. Synchronization between endpoint manager and clients isn't real-time, so there is a bit of a lag between installation and the correct status being displayed. If I wait a few more minutes, it correctly displays the install status.
Hallam is a software architect with over 20 years experience across a wide range of industries. He began his software career as a Delphi/Interbase disciple but changed his allegiance to Microsoft with its deep and broad ecosystem. While Hallam has designed and crafted custom software utilizing web, mobile and desktop technologies, good quality reliable data is the key to a successful solution. The challenge of quickly turning data into useful information for digestion by humans and machines has led Hallam to specialize in database design and process automation. Showing customers how leverage new technology to change and improve their business processes is one of the key drivers keeping Hallam coming back to the keyboard.