Microsoft would like Office 365 tenants to use the Click to Run (C2R) version of the Office desktop applications because C2R is automatically updated with new features. We like C2R, but we also like knowing what’s installed on user workstations. Here’s how to check the Click to Run configuration with PowerShell.
The latest version of Teams supports the ability to create org-wide teams, but only if your tenant has fewer than 1,000 accounts. It’s a neat idea, if you can use it, but if you have more than 1,000 accounts, there are other ways to foster company-wide communications.
Details of how Microsoft IT manages its deployment of Office 365 Groups were discussed at the recent Ignite 2018 conference. It’s a good idea to write down the basic framework of your Office 365 Groups deployment, if only to understand how all the different policies and features fit together.
The new Microsoft 365 roadmap features the ability to download items (filtered or the entire roadmap) to a CSV file. You can then open the file with Excel or pour its contents into Power BI to analyze the roadmap to your heart’s content. That seems like a good thing.
If you read yesterday’s article about the new team management functionality in the Teams and Skype for Business Online Admin Center, you might be interested to hear what Microsoft has to say on the topic. Head over to Ignite, in person or virtually, and you’ll find out.
As expected, Microsoft has announced the unified Microsoft 365 Roadmap that includes all the technologies that are part of Microsoft 365: Office 365, Enterprise Mobility + Security and Windows 10. The new roadmap comes also with a new web site and a new URL (Note: the Old Office 365 Roadmap Url is still live, but …
Microsoft has released four new administrative roles to help Office 365 tenants manage Teams. It’s a good thing and we were able to include the news in the September 20 update for Office 365 for IT Pros.
A demo to show how easy it is to use PowerShell to manage Office 365 Groups and Teams was progressing nicely at the UK Evolve conference when a problem happened with code that used to run perfectly. Sounds like a normal programming situation, but in this case, Microsoft had changed the format of Office 365 audit records for Azure Active Directory operations. That’s not so good. What’s worse is that some essential data is now missing from the audit records.
Records featuring an account called BOXServiceAccount appear in the Office 365 audit log. Not much information is available about the account, but it’s all OK because it’s used to assign administrative roles to Office 365 accounts.
Office 365 tenant administrators can use different ways to access user data. Shouldn’t you have a policy to govern that access?