Maintaining accurate Azure AD User Account manager links is important because many Microsoft 365 features like the Organization chart in Teams, the user profile card, and Outlook's Org Explorer depend on the information. This article covers how to use PowerShell to maintain the manager-employee links.
On the show this week, we're delving into the recent Microsoft Cloud outage, new Exchange Security patches, new Teams Feature, plus much more!
Creating a Planner plan from a template allows a team working on a project to start working with the plan without creating a new plan from scratch. This is particularly useful when the same basic plan is used on multiple occasions. In this article, Sean Mcavinue shows you how to do this with some PowerShell Automation!
After much humming and hawing, Microsoft reset the retirement date for several old Azure AD modules to March 30, 2024. The nine-month extension is there to help customers convert scripts to use the Microsoft Graph PowerShell SDK or Graph API requests. On the upside, the extra time is good as it creates space to migrate scripts. On the downside, there's still some challenges in converting from the old Azure AD modules.
In the first article about using the Planner Graph API to report details of plans in a Microsoft 365 tenant, we explained the basics of how to extract data about plans, tasks, and buckets to create a report using a PowerShell script. Now we take the lessons learned a step forward to illustrate the principle that with access to data, the possibility for creative use of that data is boundless and upgrade the script to include a listing of incomplete tasks and per-user analysis of incomplete tasks for each plan.
The arrival of application permissions for the Planner Graph API makes it much easier to write PowerShell scripts to automate administrative operations like reporting Planner data. This article describes a example script that uses the Planner APIs to gather and report information about the plans belonging to Microsoft 365 Groups.
Many people use the Windows Task Scheduler to run PowerShell scripts. The Task Scheduler works, but it creates a dependency on a specific workstation and isn't as secure as you might like. Running Microsoft 365 PowerShell scripts in Azure Automation is a much better idea. It's time to dump the Task Scheduler!
Most Microsoft 365 user accounts don't need access to Exchange Online PowerShell. It's an administrative tool that end users don't get much value from. In this article, we explore the best way to disable Exchange Online PowerShell using a script that can run interactively or as a scheduled Azure Automation runbook (the best way for automatic management).