So, now we have the capability in the Microsoft 365 admin center too! While this method to manage security is effective and is absolutely still a good option, we recognized that many admins don’t regularly use the Azure Portal–some never do. John: Managing MFA, security defaults and Conditional Access policies has traditionally been performed through the Azure Portal. So how do admins use this to manage MFA, Security Defaults or Conditional Access policies, and how is that changing exactly? Prior to this, and with the rollout of Security Defaults in 2019–2020, our admins had to go to the Azure Portal to manage Security Defaults, some didn’t know where to find it initially or weren’t expecting MFA–it led to a lot of support calls.īrian: Wow, so the new Configure Multi-Factor Authentication feature will make it easier for Microsoft 365 admins to secure their users. So, with all this in mind, making it as easy as possible for admins to secure their tenant and manage MFA are the reasons behind the creation of the new Configure Multi-Factor Authentication feature in the Microsoft 365 admin center. The latest news is that security defaults is now rolling out in 2022 for existing Microsoft 365 tenants who have not already applied MFA and have yet to enable security defaults, Conditional Access policies, or per-user MFA settings. For these tenants, we continue to recommend Conditional Access policies or per-user MFA settings. Usually, it’s because some users were still using Basic authentication in some way or had service accounts that can’t use two-factor authentication. Security defaults requires two-factor authentication for all users and requires a user to register for MFA within 14 days.įor some admins, this didn’t work for various reasons. That meant that all tenants created after October 22, 2019, had the Security Defaults policy applied by default-unless the tenant admin disabled it after tenant creation. John: I’d like to share a little background first… as part of an ongoing effort to reduce compromised accounts, Microsoft has implemented security policies that ensure our customers are secure by default.įor example, the rollout of the Security Defaults policy for newly created Microsoft 365 tenants on all license levels began in 2019 and finished in 2020. What are you working on in the security area with Azure AD engineering for Microsoft 365? I also watch for emerging issues our customers are reporting and work with the team to get ahead of those with solutions.īrian: Security is definitely top of mind for a lot of our customers. I spend most of my time working on feature and service improvements, self-help and diagnostics, and troubleshooting assets for our support engineers. This includes scenarios with security, multi-factor authentication (MFA), single sign-on, and synchronization with Azure AD Connect. My name is John Inman and I’m a Senior Supportability Program Manager covering Identity and Azure Active Directory (Azure AD) with Microsoft 365. We’re excited to welcome one of our Microsoft 365 Supportability team members to talk more about how to manage security settings for users.īrian: Welcome John! Let’s start with a little about your role in the CSS Modern Work Supportability team and what you’re focused on these days. We also spend a considerable amount of time working to improve the supportability of Microsoft 365 services to reduce the number of issues you experience as well as minimize the effort and time it takes to resolve your issues if they do occur. Our support services extend across the entire lifecycle and include pre-sales, onboarding and deployment, usage and management, accounts and billing, and break-fix support. The Microsoft 365 commercial support team resolves customer support cases and provides support to help you be successful and realize the full potential and value of your purchase.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |