by Peter Baddeley | Jul 25, 2019 | Blog, Lifecycle Management, Provisioning
The pros and cons of a naming convention for Microsoft Teams Does ProvisionPoint 365 allow me to set a naming convention for Microsoft Teams? This is a question that we are regularly asked during demos, and of course the answer is yes. There is then typically a...
by Peter Baddeley | Jul 17, 2019 | Blog, Lifecycle Management, Office 365 Governance
Microsoft Inspire 2019 – The Year of Teams? Vegas Baby! It is the middle of July and many people in the Microsoft ecosystem are in Las Vegas for Microsoft’s annual partner hyper-summit, ‘Inspire’ (nee ‘Worldwide Partner...
by Peter Baddeley | Jul 16, 2019 | Blog, Lifecycle Management, Office 365 Governance
Do you really need an “Intranet-in-a-box” solution for SharePoint? Office 365 Overload There appears to be an influx of Intranet-in-a-box products for SharePoint, not surprising considering SharePoint dominates the corporate intranet market and the fact that the...
by Peter Baddeley | Jun 26, 2019 | Blog, Compliance, Lifecycle Management, Office 365 Governance
OneDrive Grows Up, Gains Enterprise Security Personal Governance Governance is not just about how your systems and services are managed and administrated, it is also about how the information held within your services is used, controlled and stored. In an announcement...
by Peter Baddeley | Jun 21, 2019 | Blog, Lifecycle Management, Office 365 Governance
Why your users will hate Teams and what you can do about it Over the years I have been working with SharePoint I have lost count of the number of people who tell me they hate it. This includes users on a training course, stakeholders at first meetings, family members...
by Peter Baddeley | Mar 15, 2019 | Blog, Lifecycle Management
What is the lifecycle of a Microsoft Team? There are several challenges with deploying Microsoft Teams to an organisation and one of the most significant is how to avoid an endless sprawl of Teams. One key component of this particular challenge is when to archive or...