Tools

Whenever a user or the synchronization makes a change in Delegate365, this is logged. Logging is a collection of changed properties of an object. Since many different things can happen, logging depends on the action. See more here. Delegate365 protocols the changed object properties or assignments to an object. Through the service-oriented architecture, it can take up to 5 minutes till actions are visible in the audit logs. Logs are available for users who have permission to the corresponding Logs modules. For scope admins, usually the Quick Audit OU´s menu is available to see changes of their own objects as follows. ...

The Governance Toolkit 365 (GT365) is a software-as-a-service solution that offers insights into a Microsoft 365 tenant and is part of the Microsoft Applied Cloud Stories initiative (#AppliedCloudStories). GT365 reads cloud data, stores the data and offers IT administrators monitoring and reporting functions to get a tenant overview at a glance, for example as a newsletter, in Power BI, as API or as a Bot that can be integrated in Microsoft Teams. The GT365 workloads are fully processed in Microsoft Azure using serverless computing. Here are some architectural insights on how to avoid throttling and how to use fan-out functions. ## The application ...

There are several ways to get the number of assigned Microsoft 365 licenses in Delegate365, depending on the administrator´s permissions policy and the OU assignments. See all methods listed here. Licenses / License report: This module shows den current status of licenses per OU as shown here. First, the Delegate365 licenses are shown. Below, every OU is listed in a box with it´s numbers per object type (such as Users, Groups, Shared Mailboxes, etc.) and the numbers of Microsoft 365 licenses that are assigned to users in that OU. If there are license quotas set, the quota is shown as well. This module is aimed at administrators, the Delegate365 licenses and number of managed objects are shown as well. Licenses / License statistics: This module is aimed for Scope Admins and shows the numbers of used Microsoft 365 licenses as follows. Licenses / License aggregation: For customers, it is often important to know later, on which day in which unit how many licenses are assigned. To enabled such a reporting, Delegate365 stores the assigned Microsoft 365 licenses on a daily basis. In the License aggregation module, administrators can filter for their OU´s and a date range. In the result list, all assigned Microsoft 365 licenses are shown for the OU and per day. This list can be easily exported using the CSV and Excel symbols in the top right of the list as shown in the screenshot below. This list shows a very detailed historical use of the licenses and quotas. Note: In this chronicle you can go back to the beginning where you started working with Delegate365, not only 30 or 90 days as Microsoft 365 stores data! Reports / Delegate365: The report License statistics in the Delegate365 section at the end of the report´s list shows the numbers of assigned Microsoft 365 licenses as well. License statistics: This reports is an exported list including the current numbers of assigned licenses and quotas per OU as shown in the Excel export here. Note: If you are interested, what objects are assigned to an OU, check out the OU overview report. This export includes all objects in a line per OU: users, groups, etc. The report Active user detail in the Office 365 section shows assigned licenses per service for a simple analysis: Note: To see a list of available reports with samples, see Delegate365 on GitHub Reports / Delegate365 / notifications: Note that every admin can choose when to receive a report in the Schedule dropdown. Available options are* Run now, Run weekly (each Monday) *and Run monthly (each 1st). This allows to automate the report generation on a individual user basis. Note: The Portal admins controls how the notification is sent to the users: Send notification with link to the Delegate365 reports page, Send notification with the report as attachment, and Send a notification with a direct download link to the report, which is valid for 24 hours. Our recommend method is to use the last option with the 24-hours link. See more at Delegate365 changelog version 8.4 - New Report notification settings. User properties / Notifications: Another option is to set the Daily Notifications to Yes in the user properties. Click on your user name in the top right corner and select Properties. Turn on the daily notifications and enter the email address to send the report to (usually that would be your work account address you use to manage Delegate365). Then, click Save. The daily notification function generates a report every night that is sent to the provided mailbox. The admin gets an overview of the assigned users of his assigned OU´s. The email is sent with the subject “D365 daily notification” and looks similar as here. This notification includes a section for every OU showing the current numbers of assigned Microsoft 365 licenses and managed objects on a daily basis automatically. Every admin can select this option if needed. So, Delegate365 provides several methods to get and to export license statistics, even historical data. ...

Microsoft Graph PowerShell module made it to the PowerShell Gallery! So, now you can try it out on your computer by simply running the Install-Module Microsoft.Graph.Authentication command. See more here. Microsoft Graph is the key to Microsoft 365 system. This OData interface allows to get and modify data of objects such as users, groups, their data and the tenant. Find out more at aka.ms/graph. Announced at the last Microsoft Ignite conference, admins can now use the Microsoft Graph PowerShell module directly from the PowerShell Gallery. See more details at Microsoft Graph PowerShell SDK (Preview) on GitHub. So let´s start our quick overview. ...

Delegate365 allows to split a Microsoft 365 tenant and to delegate management of assigned objects. With synchronization rules, licenses can be added or removed automatically. This works together with license quotas. In this article we show an example. Scenario: Here, we have a demo tenant and two administrators in Delegate365: Admin and AdeleV. The Admin can manage the OU´s “Seattle” and “New York” and has the role “Portal Admin”. AdeleV has the role “Scope Administrator” assigned and she can manage OU “New York” as we see in the Delegate365 Administration / Administrators menu. ...

Delegate365 has continued to evolve over the past few years. See the timeline of the Delegate365 versions in this graphic. atwork started the development of Delegate365 (www.delegate365.com) in early 2013 as an Add-On for Office 365. Many functions have been added since then. Here you can see the graphic of the Delegate365 versions timeline as of today (click to enlarge). On average, a new Delegate365 version is deployed every 3 months. Delegate365 is operated as SaaS, so updates usually happen automatically. For versions that require additional permissions, a Delegate365 administrator must run a setup once on request. You can find the Delegate365 version details in the corresponding articles here. The current version is Delegate365 v8.5. The next update will be Delegate365 version 9.1, planned for February 2020. ...

Delegate365 version 8.5 is an update to the extensive Delegate365 version 8.4. This update includes a new sync operation “Sync with security group” and some sync fixes. See a description here. New “Sync with security group” mechanism: In Administration / Sync rules, this option allows to synchronize all members of a Security Group with assigned members of an OU. After a sync, only the members of a security group are assigned to an OU. Removed members will be removed from an OU, new members are added. See a full description of this sync feature at Sync with Security Group. ...

Delegate365 version 8.5 comes with an updated sync operation for the option “Sync with security group”. This option allows to achieve a match between (specific) Office 365 security groups and Delegate365 OU´s. In short, this means that the members of a Security Group control the assigned members of an OU, and after a sync, they are identical. See a description of this sync feature here. Sample scenario To describe the “Sync with Security Group” functionality, here´s a demo. In our organization, there are branches in 3 locations: *Seattle, New York, *and London. We want to have users in some locations automatically assigned to OU´s in Delegate365. For that purpose, we are using Security Groups in Office 365 and add the users as members to these groups. So here´s the detailed scenario. ...

Delegate365 is using the Microsoft 365 and Azure standards to sign-in and to communicate with the Microsoft APIs. Here´s the best practice how to secure your environment for using Delegate365. 1. Secure your Microsoft 365 tenant Microsoft 365 provides a bunch of features to harden a tenant and to raise the Secure Score. Every administrator should start improving the security with setting Conditional Access, MFA, and policies. You can learn more about Microsoft Secure Score here. This demo tenant screenshot above is not properly configured and should definitely be secured. If your need support, we got you covered, see our Enterprise Security & Compliance Workshop offering. ...

PowerShell helps automate processes, especially in the Microsoft 365 world. That´s true for the Microsoft Power Platform as well. See how to access PowerApps and Flow with PowerShell here. So, here´s a very quick introduction for using PowerShell with PowerApps and Flow. Find the full documentation at PowerApps cmdlets for administrators. Install the PowerShell modules Install the PowerApps (preview) module from the PowerShell Gallery once with the following PowerShell statements as Administrator on your machine: ...