See more about SharePoint Conference 2019 here.
After the introduction of the Office 365 Groups and Microsoft Teams Governance Toolkit and with the necessary requirements we are now looking into Azure Functions. In our group and team provisioning scenario, we need a little code for provisioning of an Office 365 group and a Microsoft team. Serverless computing with an Azure Function provides the optimal solution for that. Follow these steps to create the function we need for our workflow.
In part 1 of this series we described the scenario for our Office 365 groups governance toolkit. In this part we will setup a workflow for the Office 365 and Microsoft Teams provisioning. Workflows help to follow specific processes for a successful collaboration.
Offering self-services for users is a key to reduce workloads on the IT department and to allow users to cover their requirements quickly while the organization's policies are enforced during the process. A frequently asked request is how to provision a new Microsoft Team in Office 365 in a secure and monitored way. See how this can be implemented here.
To allow an app to create a Microsoft group or team programmatically in a workflow, we will use the Microsoft Graph API, Azure Functions and Flow or Logic Apps. With these technologies, we can create powerful workflows to offer a self-service for users to create a team when needed, approved by the manager and being provisioned with all the necessary properties and permissions.
IT-Governance is an important topic, especially in large organizations. At Microsoft Ignite conference, we showed the "Groups Governance Toolkit" with a bunch of useful tools to regulate and monitor Office 365 groups and Microsoft Teams. Here, we will show the step-by-step guidance how to implement that toolkit with Microsoft 365 and Microsoft Azure. Let's start with an overview what topics we cover in this article series.
This first article describes how to add some code to PDPs and provides a sample how to hide a field depending on the value of another field.
As announced in Delegate365 changelog version 8.1-Many new features, this version brings PowerShell support for administrators. All Delegate365 admins can use the PowerShell module if the access is granted by Portal Admins. See the How-To here.
This December, the 9th Thrive Conference will take place in beautiful Slovenia. Thrive conference impresses with great content and well-known speakers in the middle of central Europe, this year in Slovenia's capital Ljubljana from December 4th to 5th, 2018. See the conference details at www.thriveconf.com.
Delegate365 runs completely in Microsoft Azure, in a region of the customer's choice. So, for US-based companies, Delegate365 is hosted within the United States of America, for EU-based customers, Delegate365 is hosted within the European Union, etc. Since we sometimes get questions about the location of the Delegate365 solution, we want to inform about the hosting options here.
We were happy to be part of the 4th SharePoint Saturday organized by sug.cat in Barcelona last weekend. #SPSBCN took place on the 27th October at IQS, Institut Químic de Sarrià, on the hills of the beautiful city of Barcelona and offered almost 20 sessions about Microsoft 365 and Azure.
Paris is always worth a trip, especially when the Modern Workplace Conference Paris 2018 takes place! So, we just returned from #MWCP18 that occurred from Tuesday, 16th to Thursday, 19th October at Microsoft France in Paris. Modern Workplace Conference Paris offered a pre-day and two conference days with four tracks and more than 50 sessions, delivered by Microsoft Corp speakers, IT-experts and Microsoft MVPs.
These days, the next major Delegate365 version 8.1 is released. In that new version, there are a lot of new and improved features available for all Delegate365 customers. The menu has been restructured, permission policies allow to define granular rights and license policies simplify the set of licenses for Scope Admins. Furthermore, there are a bunch of useful improvements and the Delegate365 PowerShell module is available. See the details here.
With Delegate365 version 8.1 and the new permission policies, there come the new license policies as well. In previous versions of Delegate365, Admins could restrict the Office 365 licenses and plans for each Scope Admin. Now, the license set is replaced by a license policy that can be assigned to multiple administrators. See here, how this works.
When we started with Delegate365 five years ago, basic permissions were sufficient to control what features can be used by Scope Admins. Since Delegate365 evolved with more functionality and we received requests from our customers, it was time to renew the permission control to a more granular level. So, the existing permissions have been replaced with permission policies. With Delegate365 version 8.1, each Administrator gets a permission policy assigned that controls on a very granular level, what modules and features can be managed. The new menu structuring is part of that functionality. See how the permission policies work and how existing permissions are converted here.