Implementing Multi-Factor Authentication
Configuring Application Access
Implementing Access for External users
The course is part of this learning path
This course has been designed to teach you how to manage Microsoft 365 access and authentication. The content in this course will help prepare you for the Microsoft 365 Identity and Services exam.
The topics covered within this course include:
- Managing Authentication
- Implementing Multi-Factor Authentication
- Configuring Application Access
- Implementing Access for External Users of Microsoft 365 Workloads
Who should attend this course?
- Those who are preparing for the Microsoft 365 Identity and Services exam
- Those looking to learn more about Microsoft 365
- To learn how to configure and monitor authentication
- To learn how to administer MFA and report on its utilization
- To learn how to configure application registration and use Azure AD Application Proxy
- To learn how to use Azure Active Directory B2B to add and manage external users
To get the most from this course, you should at least be familiar with the Microsoft 365 offering and have a general understanding of its features.
- [Narrator] Leveraging Azure MFA in the cloud, you can manage the user and device settings. For example, as an administrator, you can require users to re-provide their contact methods, you can delete app passwords, and you can require MFA on all trusted devices. Requiring the user to re-provide their contact methods forces the user to complete the MFA registration process again. Non-browser apps that the user has access to will continue to work however, if the user has app passwords for them. That said, you can delete a user's app passwords by also checking the box next to delete all existing app passwords generated by the selected users. The option to delete a user's existing app passwords allows the admin to delete all of the app passwords that a user has created. Any non-browser apps that were associated with the deleted app passwords will stop working until a new app password is created. When using Azure Multi-factor Authentication, you can allow your users to mark devices as trusted. What this does is permit users to opt out of two-step verification for a set number of days on their regular devices. However, in the event that an account is compromised, or if a trusted device gets lost, you need to be able to remove the trusted status and require two-step verification again. Checking the box for restore Multi-Factor Authentication on all remembered devices allows you to do this. When you restore MFA authentication on all remembered devices for a user, the user will be challenged to perform two-step verification the next time they sign in, regardless of whether or not they chose to mark their device as trusted. In the next demonstration, we'll walk through the process of managing Multi-Factor Authentication for our users.
About the Author
Tom is a 25+ year veteran of the IT industry, having worked in environments as large as 40k seats and as small as 50 seats. Throughout the course of a long an interesting career, he has built an in-depth skillset that spans numerous IT disciplines. Tom has designed and architected small, large, and global IT solutions.
In addition to the Cloud Platform and Infrastructure MCSE certification, Tom also carries several other Microsoft certifications. His ability to see things from a strategic perspective allows Tom to architect solutions that closely align with business needs.
In his spare time, Tom enjoys camping, fishing, and playing poker.