Microsoft has extended the deprecation date for the Azure AD license management cmdlets to March 31, 2023. After that time, the cmdlets won't work. The strong recommendation is to replace all the old Azure AD and MSOL license management cmdlets in scripts with Microsoft Graph PowerShell SDK cmdlets or Graph API requests. You have an extra 7 months to do the job, do there's no excuse!
In episode 3 of season two, Paul Robichaux and Steve Goodman chat about a flurry of new Microsoft Teams features - including the long-awaited Teams Connect shared channels going into general availability, plus Microsoft's headline conference for IT professionals is back in-person - but will it be the same?
After spending some time to better understand how Azure AD Connect Group Writeback v1.0 works with the attribute flow and some possible use cases, I’ve come up with some practical pointers for you to understand as you consider a deployment.
You just activated the Exchange admin role (or any other role) via Privileged Identity Management (PIM), but the Microsoft portal still indicates that you have insufficient permissions to perform your task. Don’t panic, this blog will help you to load freshly activated permissions faster.
On July 6, Microsoft announced the public preview of Azure AD Group Writeback. As is usual with announcements of this nature, it created several questions. In this article, I want to explain some higher-level details about the new feature.
In April, we had over 450 attendees join and ask questions in our TEC Talk on lessons learned from Office 365 tenant to tenant migrations. Get the highlights and the Q&A to the top questions asked!
Conditional access policies grow and change as the tenant grows and changes, but not all of the old policies, groups and assignments are not always tidied up, leaving complex web of policies that target different groups or apps. To gain insights into this mess, I created a PowerShell script to document not just Conditional Access policy settings, but also detail who is impacted by each policy and why.
I used Microsoft Defender for Cloud Apps in a project with Microsoft 365 E5 licenses and realized it’s a handy and powerful tool at a reasonable price even if purchased as a standalone product. This post will outline practical use cases for using it to monitor and enforce restrictions on Microsoft 365 apps and some third-party apps to reduce the likelihood of information leakage.
Security Defaults is a control in Azure Active Directory which has been around since 2019 and is enabled by default on new tenants created after October 2019. Microsoft recently announced they will now start turning on Azure AD security defaults for existing tenants. Throughout this blog we will explore what this means and if Security Defaults is the right fit for your organization.
Practical365.com is a proud sponsor of The Experts Conference 2022. TEC is all about providing practical Microsoft 365 and Hybrid Activity Directory security, administration, and migration training without the fluff. All content is sourced from the very best in these fields, including Practical365.com authors, Microsoft MVPs, and Microsoft engineers.
Microsoft plans to enable Azure AD Security Defaults for Office 365 tenants created prior to October 2019. The move will protect an additional 60 million Azure AD accounts against common attacks by enforcing MFA more broadly. It's a big deal in terms of improving the overall security posture of Office 365. If you don't want to use Security Defaults, tenant administrators can switch them off.
Any discussion about securing Microsoft Teams can rapidly descend into a detailed debate about different policy settings. But when you focus on what really needs to be done, it's all about making sure that user access is secure, external access is controlled, and individual teams are managed. Easy!
