Changelog

Click here if you like to subscribe the ChangeLog as an RSS feed.

Delegate365 changelog version 7.4-additional reports with risk events and Microsoft Teams, OneDrive shared with and groups as members

Thursday, February 15, 2018

With Delegate365 version 7.3 a new reporting engine was introduced. With this update, additional reports are available in Delegate365 version 7.4. The new reports deliver a new report category with risk events, as for example impossible travel risk events or suspicious IP risk events, new Microsoft Teams statistics reports and more. Also, OneDrive usage per user and Shared-With information is now available as a report. Mail Enabled Security Groups can now be assigned with permissions in Resources (rooms and equipment mailboxes) and Shared Mailboxes. See the details and descriptions of all reports here.

  • Important: Since the new reports require additional permissions in the Office 365 tenant, a Global Administrator needs to run a new Delegate365 setup once. Please see Delegate365-(Re)run the setup for a step-by-step manual. This step is necessary after the update to Delegate365 v7.4 was done.
    You need to have a Global Administrator without MFA enabled to run the setup and to accept the new Delegate365 consent:
    image
    So, after the setup, login with the Global Administrator and accept the new consent for all users in your tenant – otherwise no one can sign-in and use the Delegate365 app.
  • Additional reports "Risk events": The list of available reports now offers six new reports showing threads to the Office 365 tenants – filtered just for the entitled OU’s of the signed-in administrator.
    image
    See Azure Active Directory risk events for info about the protocolled risk events in an Office 365 tenant.
  • Additional reports "Microsoft Teams": This is a new group offering two reports from Microsoft Teams.
    image
  • Available reports: With Delegate365 version 7.4, the following reports are available. (NEW) indicates new reports compared to v7.3. See all reports with a short description and a sample output summarized here (click on the image to enlarge it).
  • Risk Events (NEW)
    • Anonymous IP Risk Events (NEW)
      This report shows successful logins from anonymous proxy IP address that could be used to hide the real device’s IP address for malicious intent.
      image
    • Impossible Travel Risk Events (NEW)
      This report shows sign-ins from geographically distant locations, that are also atypical for the user, given past behavior.
      image
    • Leaked Credentials Risk Events (NEW)
      The Microsoft leaked credentials service acquires username and password pairs by monitoring public and dark web sites and reports stolen credentials in that report.
      image
    • Malware Risk Events (NEW)
      This report shows sign-ins from devices infected with malware, that are known to actively communicate with a bot server by IP address comparisons.
      image
    • Suspicious IP Risk Events (NEW)
      This reports shows IP addresses from which a high number of failed sign-in attempts were seen, across multiple user accounts, over a short period of time.
      image
    • Unfamiliar Location Risk Events (NEW)
      After an initial learning period of 30 days,this reports shows user logins from unfamiliar locations not close to known, familiar locations.
      image
  • Office 365
    • Office 365 active user detail
      This reports shows all users that are active (not deleted) and their current licenses status and the last activity date per service.
      image
      image
    • Office 365 groups activity detail
      This report shows the usage of the Office 365 groups, the storage size in SharePoint, number of messages in Exchange, last activity date and more – all you need to know about your Office 365 groups.
      image
      image
    • Office 365 activations user detail
      This report delivers activated Office 365 licenses per user. If more information is existing, the license activation date and installed clients are shown.
      image
  • Microsoft Teams (NEW)
    • Teams device usage user detail (NEW)
      Shows the devices used for accessing Microsoft Teams per user for the selected time period.
      image
    • Teams user activity user detail (NEW)
      This report delivers the users and when they last accessed Microsoft Teams. Additionally, the assigned user licenses are shown.
      image
  • Skype for Business
    • Skype for business activity user detail
      This reports shows Skype for Business statistics per user, for example the number of conferences, the sum of minutes consumed, the number and date of the last participations and much more.
      image
      image
      image
      image
  • Yammer
    • Yammer activity user detail
      This report shows the last activity date per user and the number of posts written, read and liked in the selected time period.
      image
  • SharePoint
    • SharePoint activity user detail
      This report shows the last activity date per user and the number of files and pages visited in the selected time period in SharePoint Online.
      image
  • OneDrive
    • OneDrive activity user detail
      This report shows the last activity date per user and the number of files accessed and how many files have been shared in the selected time period in OneDrive for Business.
      image
  • Exchange
      • Outlook activity user detail
        This report shows the last activity date per user and the number emails sent and received and read in the selected time period in Exchange Online.
        image
      • Outlook app usage user detail
        This report delivers which apps users are using for accessing their mailbox, including clients, Web, IMAP, SMTP and POP3.
        image
        image
      • Outlook usage detail
        This reports delivers detailed information about mailbox usage as the mailbox size and number of items, the quota and warning limits per user in the selected time period.
        image
        image
    • OneDrive files report generation: In the users list, a new menu is available for the selected user: Report OneDrive files generates a report about all files of the user that are existing in the personal OneDrive for Business storage and what files are shared with whom. A use case for this report is that if a user leaves the organization, the admin can see what files have been shared with other users. Then, these common files could be transferred to another user’s OneDrive, SharePoint site or similar. So, the report shows these shared files as well.
      image
      A pane opens asking for a notification email address. The signed-in admin is automatically existing in the email field. The generation of the report can take a longer time, if the user has thousands files stored, each file must be checked and looked up, if it was shared or not. So, a notification makes sense in most cases to see the report, when it’s available.
      image
      When clicking Submit, the report engine gets a new job and the OneDrive files report task is visible in the reports menu in the Scheduled reports box.
      image
      Once generated, the report can be found in the Finished reports box where it can be downloaded.
    • OneDrive files report result: The OneDrive files generated reports delivers all files of the user’s OneDrive storage. The report shows one (or more) line(s) per file with name, path, size, and modified date and with whom the file is shared with.
      image
      Basically, SharedWith always shows the file owner, in this sample, AdeleV. If the file is shared with other users, there is a line for each user with his Roles is added to the report as seen here.
      image
      The WebURL allows to open a file directly with the Office Web apps to have a quick look at the file (if the user has permissions). ParentPath shows the location of the file in the folder structure to find it easily. So, this report delivers all files and their status of a user’s OneDrive storage.
      In Excel, filtering is simple: If you want to see all shared with, filter the Roles for all other roles as "owner", here only "read":
      SNAGHTML858dc41
      Then Excel shows just the other users and the files they have access to. Excel provides more methods for summarizing, grouping and pivoting if needed.
    • Support for group membership: In Office 365, it’s possible to add a Mail Enabled Security Group as member to user’s mailboxes, as delegated user in Resources (rooms and equipment mailboxes) and Shared Mailboxes. This does not work for other group types (see Working with Exchange Mailboxes and Groups as members), but for Mail Enabled Security Group only. So, this feature has been added to Delegate365. With this update, it’s possible to select a Mail Enabled Security Group from the people picker as well.
      image
    • Using group membership: You can create a new Mail Enabled Security Group in Delegate365 in groups / distribution groups (basically, a Mail Enabled Security Group is a Distribution Group in Office 365). Ensure that the "Mail enabled security group" switch is set to Yes.
      image
      Tip: Since this is an Exchange object, it can take some minutes, until the new group is visible.
      Then, the (new) Mail Enabled Security Group can be added as member for a user’s mailbox delegation. In this sample, we assign the group "MailEnabledSecurityGroup1" with the permission Full Access to AdeleV’s mailbox. All members of that group have access to that mailbox.
      image
      The same functionality is available for Resources and Shared Mailboxes as well.
      image
      This new group-as-member feature is compliant with Office 365 and simplifies management and allows all members of the assigned group to access the mailboxes.
    • Fixes: Some labels and descriptions have been updated and the CSV and Excel download icons have been changed.

    Delegate365 version 7.4 provides additional reports and new features. The update time will be planned accordingly with our customers. New Delegate365 tenants will get this version automatically starting by end of February.




    Delegate365 changelog version 7.3-new reports

    Monday, February 12, 2018

    The newest version 7.3 of Delegate365 provides a complete new reports module that replaces the old reports section. See the benefits and the details of the new Delegate365 reporting engine and how to use it for all your Delegate365 admins with just their entitled data. Learn about the details here.

    • New reports menu: The old reports menu was replaced by the new module. Now, there are four boxes with a description, the available reports, scheduled reports and finished reports. All Delegate365 Admins can now select from new reports (1 and 2), activate a notification when finished (3) and start a report job with the Submit button (4). This creates a task in the schedules reports list (5). A job picks that task and executes it after a couple of minutes. When the report has been created, a notification can be sent to the report owner and the report shows up in the finished reports list (6). Refresh updates the reports boxes (5 and 6) with the current status if needed.
      image
    • Reports scope: All reports are filtered just for the entitled OU’s of the signed-in admin. So, the report engine collects the requested data, looks up the entitled objects and delivers just a subset of all tenant data. Scope Admins can now use these reports for collecting data reports just for their relevant data. For example, if the logged-in Admin is entitled for OU’s Seattle and New York, then the generated reports just sh ows users, groups and actions in these two OU’s. Any data outside of these OU’s is not shown.
    • Options: Some reports can be filtered for a time range from 7 days up to 180 days, depending on the report type. The time range selection gets active or inactive then.
      image
    • Notifications: Since the generation of a report can take some minutes, it often makes sense not to wait for the result, but let the report engine send a notification to an email address specified in the notification field.
      image
      The email comes with a subject "D365 Report engine" and a message as "Hi, this is a notification sent from your Delegate365 solution.Your report #64 OneDrive activity user detail was created successfully".
    • Flow and operation: The user selects a report, the time range and if a notification shall be sent. When clicking the Submit button, a task is generated and the report request shows up in the scheduled reports. Each job gets a current number, #64 in this following sample (1). This identifies the report, along with the report name, the selected filter and the creator of that task. Every users sees just his own report tasks. So, the current number can be not continuously.
      There is a time span of about 3 minutes until the report job picks up the task. Within that time, the user could cancel the job with the trashcan icon (2). This is useful, if you find out that the scheduled job was a wrong report or the filter is not correct. Then, it makes no sense to execute the original report creation, but cancel it and create a new report job.
      image
      Once a job is done, the resulted files can be downloaded (3 and 4). Report files can be deleted with the trash icon (4) as well anytime.
    • Generated reports: Reports that have been finished show up in the finished reports list.This usually takes some minutes. Once the job is completed, two reports are generated to download: a CSV file (a comma separated values text file)  and a XLSX Excel file. Both files can be downloaded with the corresponding icons. The file name is the ID of the job, stored in the Azure temporary storage.
      image
      With this output, data can be used in further systems for analyzing easily. This makes more sense than showing a graphics in Delegate365.
    • Generated reports availability: Reports that are generated are available for the last seven days for download. After that time, the reports are automatically deleted from the Azure storage and from the finished reports list. Reports downloads are handled with a security token that is just valid for the signed-in user and a short time frame. So, only entitled users can download the report file and abuse is prevented.
    • The CSV file can look as here: The OU name of the object is part of each record.
      image
    • The Excel file can be opened directly and shows the same data as a formatted table:
      image
    • Available reports: With Delegate365 version 7.3, the following reports are currently available:
      image
      See following sample reports by clicking on the image to enlarge it.
    • Office 365
      • Office 365 active user detail
        This reports shows all users that are active (not deleted) and their current licenses status and the last activity date per service.
        image_thumb[1][1]image_thumb[2][1]
      • Office 365 groups activity detail
        This report shows the usage of the Office 365 groups, the storage size in SharePoint, number of messages in Exchange, last activity date and more – all you need to know about your Office 365 groups.
        image_thumb[3][1]image_thumb[4][1]
      • Office 365 activations user detail
        This report delivers activated Office 365 licenses per user. If more information is existing, the license activation date and installed clients are shown.image_thumb[5][1]
    • Skype for Business
      • Skype for business activity user detail
        This reports shows Skype for Business statistics per user, for example the number of conferences, the sum of minutes consumed, the number and date of the last participations and much more.
        image_thumb[6]
        image_thumb[7]
        image_thumb[8]
        image_thumb[9]
    • Yammer
      • Yammer activity user detail
        This report shows the last activity date per user and the number of posts written, read and liked in the selected time period.
        image_thumb[10]
    • SharePoint
      • SharePoint activity user detail
        This report shows the last activity date per user and the number of files and pages visited in the selected time period in SharePoint Online.
        image_thumb[11]
    • OneDrive
      • OneDrive activity user detail
        This report shows the last activity date per user and the number of files accessed and how many files have been shared in the selected time period in OneDrive for Business.
        image_thumb[12]
    • Exchange
        • Outlook activity user detail
          This report shows the last activity date per user and the number emails sent and received and read in the selected time period in Exchange Online.
          image_thumb[13]
        • Outlook app usage user detail
          This report delivers which apps users are using for accessing their mailbox, including clients, Web, IMAP, SMTP and POP3.
          image_thumb[14]
          image_thumb[15]
        • Outlook usage detail
          This reports delivers detailed information about mailbox usage as the mailbox size and number of items, the quota and warning limits per user in the selected time period.
          image_thumb[16]
          image_thumb[17]
      • More reports will follow with the next Delegate365 update. As soon, as Microsoft reveals more features to their APIs, we will integrate them into Delegate365.
      • Old reports section: The old reports menu with sub menus for each report have been removed.
        SNAGHTML33b41c5
        This report data is no longer available from the Microsoft APIs, since they were depreciated. The new reports scale better and deliver much more functionality and useful data.
      • Fixes: If contacts had notes with more than 250 characters, the sync threw an error. This has been fixed with Delegate365 version 7.3. Also, descriptions and labels have been updated.

      We think the new reporting engine in Delegate365 version 7.3 makes sense and delivers useful and reusable data. Delegate365 v7.3 will be updated starting mid of February to all existing productive environments. Hope you like it!




      Delegate365 changelog version 7.2-additional sync rules and more

      Wednesday, January 31, 2018

      With Delegate version 7.2 there come some new and useful features especially in the sync rules. See the details described here.

      • Sync Rules: Groups OU-assignment by new name rules: All group rules now offer additional options in the Property dropdown allowing to assign a group to an OU by its name. To get the OU name out of the group name, the OU name must be the prefix of a name and a predefined separator must be used. The options include the following separators: [space] , [underscore] _, [hyphen] –, [point] ., and [slash] /.
        image
        To clarify the mechanism, the options show a sample. So, if a group Display Name is set to "New York_Group", the sync rule strips down by the separator "_" and uses "New York" as OU name and "Group" as group name. So, group "Group" is automatically assigned to OU "New York".
        image
        Take care when using a normal space character as separator: Then, the OU name can only be one word, for example: "New York Group" would result in an OU "New" and the group name is "York Group". As workaround, the OU-name could be named with a hyphen "New-York" or similar.
        That’s the purpose, to use a Display Name for automatic OU-assignment instead of object properties. Now, admins can use this feature additionally if needed for the following objects: Distribution Groups, Office 365 Groups, Contacts, Resources, Shared Mailboxes and Security Groups as marked red in the following screenshot.
        image
      • Sync-Rules: Automatic OU-assignment to OU "None": The same object types enumerated above, now offer a new, powerful switch: Assign unassigned groups to OU "None".
        Imagine, you define a rule for Office 365 groups that they are assigned to an OU in Delegate365 automatically, based on a property as CustomAttribute13 as shown below. All Office 365 groups with that property filled will be assigned to the corresponding OU. But, if there is no value filled in CustomAttribute13, a group will not be assigned to any OU.
        (Of course, Portal Admins already could manually assign objects to a specific OU in the administration / organizational units / assign module – and this still is an option.) Now, if Assign unassigned groups to OU "None" is set to Yes, all groups that are not assigned after all sync rules have been executed, will be automatically assigned to an OU with the name "None".
        image
        So, if there are groups without an OU-information in Delegate365, they will be assigned to OU "None".
        If that OU "None" is not already existing, it will be created automatically. There is no automatic administrator assignment in place, this must be done manually later if needed. The OU-name cannot be configured and is always "None". But, since OU "None" is normal OU, the name can be changed anytime. In that case, a new OU "None" would be created if one of these switches is set to yes and if there are objects to be assigned to "None".
        This switch simplifies the OU assignment, so that all Office 365 objects are automatically visible in Delegate365, even if they don’t match any sync rules. Later, Delegate365 Admins can decide what to do with these objects and manually assign them to another OU or set any properties or define any rules.
        By default, the new switch Assign unassigned groups to OU "None" is always set to No and there are no changes to existing configurations – it’s an additional setting that can be used if it makes sense for your organization.
      • Sync-Rules: new description: To match with the new functionality, the sync rules description has been extended to describe all possible features in this module.
        image
      • OU-Import: When talking about OU management, there’s now a new module in administration / organizational units / import ou’s that allows to import OU’s from a CSV file.
        image
        The downloaded sample file consists of a simple list of names that shall be imported as shown here: one OU in one line.
        image
        With Upload, this file can be selected, uploaded and then imported.
        image
        If the import was successful, the list below shows the status. If an OU was already existing, a status "OU already exists" is shown, otherwise "success". This feature is helpful if an organization exports their extensive OU-list from their local Active Directory and wants to use these names as OU’s in Delegate365 easily. As usual, the OU’s can be renamed in manage OU’s. Don’t forget to assign admins to the new OU’s afterwards in manage administrators.
      • Sync operations: new behavior: Running a manual sync is used very rarely and can take some time, depending on the tenant size and operations The following screenshot shows the old behavior (up to version 7.1). When the Sync button was clicked, the Progress box below showed the sync-progress at the bottom of the sync operations page.
        image
        We removed the Progress box. Instead, there are now two buttons for triggering the sync operations:
        Start AAD sync starts a new sync operation. The new Start MFA job allows to explicitly run only the MFA sync operation defined in the sync rules.
        image
        If a Portal Admin triggers a sync job, he needs to confirm the operation and a toast notification pops up as visual validation. The sync runs in the background.
        image
        As before, the result is shown in the Sync history. Now there’s a Refresh button to check for the latest updates manually.
        image
        With refresh, the sync history list gets updated and there’s no need for reloading the page oneself.
        The module description was moved into a box on the top as well.
      • Sync operation: (Now) there can only be one! Another reason for changing the behavior was to avoid that admins start the manual sync multiple times parallel to the (maybe long time running) automatic sync job. In the past, this could cause issues since the result maybe did not reflect the admin’s expectations since there could be multiple sync running and maybe interfering themselves.
        Now, the sync jobs runs only once. If an admin starts a new sync, a message appears that there’s already a sync job currently running as shown here.
        image
        In that case, wait till the sync job is finished and retry (or simply wait for the next automatic sync job). The Sync history box is your friend for seeing the current status and the result.
      • Office 365 groups: Hide from address list: An Office 365 group can now be hidden from the address list with the new switch in the general box as shown below.
        image
        By default, Hide from address list is set to No. Use this switch for an Office 365 group if needed.

      So, we think the new additions to Delegate365 make sense for many customers. All existing productive Delegate365 tenants will be updated starting by the begin of February. New Delegate365 trials will automatically be available in the latest version. We hope you enjoy the new features of Delegate365!



      Delegate365 changelog version 7.1-Fixes, User Interface improvements, Sync Lock, MFA and more

      Monday, December 4, 2017

      Right after Delegate365 version 7, we are releasing version 7.1 with some relevant updates. This version brings some fixes, an improved SyncOp, Sync Locking, First Start-support, a new Multi Factor Authentication automation feature, a streamlines sync rules experience, more videos and some updates. See the benefits and the details here.

      • Dashboard-First Steps: To inform Admins if the basic Delegate365 configuration is missing, the dashboard now shows a First Steps box if necessary. This essentially helps new Delegate365 admins to show the required steps to configure Delegate365. Tasks that are already accomplished are marked with a green OK icon, open tasks are shown with an orange warning icon. So, this feature basically checks if they SyncOp has been executed to update the Delegate365 cache at least once, if at least one OU is existing, if at least one administrator has been assigned to one OU and one domain and if there are users assigned to any OU (so that there are users visible in Delegate365).
        The admin can click on the task to open the corresponding page to configure the desired properties. The following screenshot shows an example with three accomplished tasks and one open task.
        image
        Once all requirements are satisfied, the First Steps box will no longer be visible (or show up again, if any requirement is missing). There is no manual method for switching the First Steps box on or off, it appears automatically to support the admin. Independently, Delegate365 checks if the connections to Azure Active Directory and Office 365 are valid as well. We think, this new feature makes sense in existing Delegate365 tenants and particularly in new ones.
      • Quicker Dashboard: The dashboard now uses dynamic loading of the content to get a better user experience. So, the start page loads faster and shows the content when available. Small animated circles are shown until the boxes are able to show their content.
        image
        This makes sense since the Office 365 service status sometimes took longer time to load and the whole page produced unnecessary waiting times. This behavior is gone now and admins get the dashboard page much faster.
      • New UI elements: Detail pages now show a back button icon on the top and bottom of a page (instead of the text link "Return to the list…") to improve the visibility for the user for going back to the previous page.
        image
      • Help and Videos: Additionally, each page got a see video link on the top (see screenshot above). This opens a short video explaining the current page (well, we are still working on the videos, so if the overview video is shown, pls. give us some time to finish that for all modules). The video integrates into the page and allows to interactively control the video. By closing or clicking outside of the dialogue, the video box closes.
        image
        We think this will help administrator to watch the functionality of the current module and to inform about the topic.
      • Help page: The Help link available on the right side in the footer now uses the same concept and shows the initial steps for configuring Delegate365 in short videos.
        image
        Again, these videos will be updated in near future.
      • Sync-Rules UI standardization: The Sync Rules allow to define conditions for automatic OU assignments and Office 365 license assignments for users and groups in Office 365. We added more features in here, but the basic user’s OU assignment interface did no longer fit to the rest of the conditions. In previous versions, the dropdowns needed to be filled with the priority of the desired rule, where the property name must match any OU name in Delegate365 (as f.e. CustomAttribute13 stores "New York" and there is an OU "New York", so that the user gets assigned automatically). In contrast, newer conditions (in the boxes below) used dynamical assignments. So, the User box has been changed to the new dynamic conditions interface as well.
        Before:
        image
        New version:
        For better clarity, now the admin can add more conditions dynamically as needed. Additionally, each rule can be set (in)active and the SyncOp can apply the rule to all users, sign-in allowed users or sign-in blocked users in the new user interface. Also, the Extended attributes have got an own box with the same options and allow a more customized filtering.
        image
        Existing customers: All existing rules are automatically converted to the new interface. There is no action needed, but we recommend to check these settings and to save this page again.
      • SyncOp performance: Since the Delegate365 synchronization fulfills a bunch of tasks, we are constantly checking and improving the SyncOp. Version 7.1 brings more error handling and better performance for specific operations as the User License Sync. So, in real world, the sync time can speed up, depending on the scenario.
      • New SyncOp Locking "There can be only one": In former versions it was possible to start a manual sync multiple times, even when a scheduled sync was already running. This sometimes lead to confusion when objects should be modified that already were updated. To avoid such conflicts, the sync now runs only once at a time.
        image
        If an admin wants to manually start a new sync while another sync is running, he gets a message informing about that. A new SyncOp cannot be started therefore. To check a currently running SyncOp, there’s a new Refresh button in the sync history box (see above) to see the status if needed. In such a case, pls. wait until the previous SyncOp is finished and then try to restart.
        image
        The sync now checks the heartbeats if another SyncOp is running or died during any process (we are working with the cloud…). A new SyncOp can be started manually after a previous sync is finished, or after 15 minutes if a timeout occurred. Usually, if a SyncOp did not fully complete for any reason, simply wait (or start a SyncOp manually) for the next run to accomplish all tasks.
      • Automation for user’s MFA status: Version 7.1 brings a new feature in the administration / sync / sync rules: A new box for setting Multi-factor authentication for users controlled by a group membership.
        image
        In the MFA box, admins can define rules in a similar way as in the rules above: By adding a condition if a user is member of a specific security group (or email enabled security group), the MFA status can be set for all users, sign-in allowed users or sign-in blocked users. The MFA status can be Deactivated, Enabled or Enforced.
        image
        Click Save at the page bottom to save all rules on that page. Users who are members of the specified security group(s) who not already have the defined MFA status set, will get the new MFA status set. This operation is not directly attached to the SyncOp, but runs all 12 hours and reports to the common audit log. So, we can categorize this feature as an own task in a technical perspective for not interfering with a running SyncOp. This allows admins to easily define custom rules for enforcing the organization’s security policies for their users.
      • UI helpers: When assigning multiple domains or OUs, now there is a (De)Select (All) checkbox to select all items below with one click. The (All) checkbox acts as toggle. Small and helpful.
        image
      • License statistics: To distinguish between no license limits and licenses quotas, the licenses / licenses statistics module now shows a dash "-" if no quota is defined. Otherwise, the defined number of the quota is shown. The same goes for the assigned users.
        image
      • License quotas filter: A new filter allows to show just rules of a specific OU or all OU’s. By default, the filter is set to Any OU and all quotas are shown. The screenshot shows an example by filtering only the rules for OU Amsterdam.
        image
      • Smaller fixes: We continuously are checking the solution and we are fixing minor issues constantly. Version 7.1 has some minor issues as text labels and validations fixed.
      • There is more to come in 2018…

      We hope you like the new features and the improvements in Delegate 365 version 7.1!

      All Delegate365 productive tenants will be updated before Christmas automatically to benefit from the improvements. There are no actions necessary on the customer side. New test tenants will automatically get the new Delegate365 version.




      Delegate365–Cleanup unused apps

      Wednesday, November 1, 2017

      Delegate365 is registered as an app in the customer’s Azure Active Directory. When a Delegate365 setup is executed, it may be necessary that a new app is registered and is used from then on. So, what happens with old apps? See how to cleanup unused Delegate365 apps here.

      Technically, the app needs permissions to sign-in the user and to read data from the tenant. If new app permissions are necessary through an update (as this was the case with version 6.5 and the new service health feature), the Delegate365 setup must be re-run. When a new app is created, the Administrator then has to confirm the app consent for his users as described here.

      Usually this is not the case for regular updates. So, in very rare cases, a new app is created during the setup. As mentioned, an app has an expiration date, but apps that are no longer used, can be removed easily if desired. Otherwise, they exist in the AAD as every other app that was registered once (and may be no longer valid). So, it’s up to the IT-Administrator to decide if he wants to perform a cleanup or not.

      For doing a cleanup, you need two things: A Global Admin in your AAD tenant and the Application ID of the current Delegate365 – you don’t want to remove the existing app, just the old ones. To get the current Delegate365 App ID of your tenant, pls. contact atwork at support@atwork.at. We will send you the App ID so that you can identify the Delegate365 app in use.

      Open the Azure Portal, your Azure Active Directory and the App registrations. Search for "delegate" and see the registered apps in the list as shown here.

      image

      In this scenario, there are 4 Delegate 365 apps existing. The currently used app starts with App ID 7dd9191f… – we do not want to remove that, but the other 3 apps (bacf…, 7b76… and 79ee…). Check the App IDs and open each app and delete it.

      image

      Repeat that step for all unused apps until just the used Delegate365 app remains. That’s it.

      If you are insecure, leave the apps untouched. If you removed the current Delegate365 app by mistake, you need to re-run the Delegate365 setup as described in the setup process.




      Delegate365 changelog version 7.0-Office 365 Groups, Alias addresses, Logging and more

      Wednesday, October 11, 2017

      We have been busy during summer time and we have been developing and testing our new Delegate365 version 7. We added new features like the support for Office 365 Groups and further useful extensions and made a technical refresh behind the scenes. So, the latest version of Delegate365 is available now and ready for updates. See the details described here.

      Delegate v7 is the successor of version 6.6. Besides new features, this is a major update since this version takes advantage of using new Microsoft APIs. So, here’s the news:

      • User Mobile Phone number fix: When a user’s Mobile phone number was modified or deleted in the additional details of a user, the changes were not visible instantly. This was caused by the Microsoft interface that the mobile phone number is an Exchange property that needs to be synced in the background. So, changes of that specific property sometimes took minutes or was lost. This has bee fixed in the latest Delegate365 version by using a new Microsoft interface.
        image
        Now, any modifications of the user’s Mobile phone number property are visible instantly.
      • Office 365 Groups: Delegate365 now can manage Office 365 groups (historically also named Unified groups sometimes) as well. You can find the Office 365 groups management in the groups menu. The module works exactly as the other group types, each Office 365 group is assigned to one OU in Delegate365. Hint: Office 365 Groups fully exist only in Office 365 and are shown as distribution groups in Exchange on premises.
        image
        If one Office 365 group is selected, Admins can modify the members and owners, as in the existing group types modules. This allows Delegate365 Administrators to create and manage the new Office 365 Groups easily.
        image
        The general box allows to set Display name, the group Alias email address (with the assigned domains), the description, the Privacy level (Public or Private), if copies of group conversations shall be sent and if sender authentication is required or not.
        image
        For modifying, click Save changes.
        If a new Office 365 group is created, the Alias is automatically prefilled in an email-safe way (as used in Delegate365).
        image

        If the email Alias is not available in the Office 365 tenant, the Admin gets a warning…
        image
        …and the Alias must be modified to an unique email address as here (project-a2).
        image
        The creation of an Office 365 group takes just some seconds. The new Office 365 group is created in Azure Active Directory, a SharePoint site is triggered to been provisioned, the email address is created in Exchange Online and members and permissions are added. So, there’s a lot of things happening in the background, but Admins can continue to work with Delegate365 right after the process.
        Info for Portal Admins: Of course, Office 365 Groups can be (un)assigned manually in administration / organizational units as the other group types…
        image
        …and there are rules for automatic OU-assignments in administration / sync / sync rules as well.
        image
      • Users E-Mail address options: Administrators can manage and add Alias addresses for their users (if permitted). After a user is selected, the EMail address menu opens the email management pane.
        image
        In here, the addresses can be modified, added or deleted. There’s a new switch for SMTP addresses: Set as primary defines if the current email shall be the primary one or not.
        image
        When the changes are saved, the primary email address is bold and SMTP is in upper case (otherwise in lower case).
        image
        Modifications are done in Exchange Online. So, it can take some minutes, till they are active in Exchange.
      • Daily notifications for Admins: Admins in Delegate365 can now get daily notifications about their manages users and groups. When clicking the user menu in the top right corner and the Properties, the user properties opens. In the new Notifications box, each Admin can switch Daily Notifications to Yes or No and set the desired email address for the notifications.
        image
        This means, that Admins receive a daily email with the numbers of objects managed in Delegate365 and if less than 10% of Office 365 licenses are available (or the licenses limit is exceeded). The email delivers an overview about all managed OU’s and looks as follows: Text in orange means warning, Text in red means limit reached or exceeded.
        image
        Each user can define if he wants to get the notification or not. By default this switch is set to No.
        Info for Portal Admins: These settings are the same as in the manage administrators admin properties, so they could be set not just by the Admin himself, but also by Portal Admins for their Admins if needed.
        image
        Warning notifications are sent if Office 365 licenses are ordered within Delegate365, or if license limits are exceeded or Delegate365 licenses are exceeded.
      • Logging extended: As described in Delegate365-Working with Audit Logs, Delegate365 stores logs on a daily and monthly basis. With version 7, there now is an additional logging to a summarized log with the name AuditLogSearch. Storage in the cloud is expandable as needed, so we thought, it’s easier to work with one single log table instead of working with monthly logs. To simply the reporting in external tools, the Power-BI file works with this single table log.
        image
        So, we recommend to use the AuditLogSearch (red box) table for dashboards and reports (so does the Power-BI file) while the monthly logs logYYYYMM (blue box) are to search for specific actions that happened in that month and the last 7 day logs logYYYMMDD (green box) for actions by day (these are deleted automatically if older than 7 days). The following picture shows Microsoft Azure Storage Explorer connected to a Delegate365 log.
        SNAGHTML2b2e95a
        See Delegate365-Working with Audit Logs for more info.
        Also, the logging itself has been extended to log all user Exchange properties modifications.
      • Upgrade from version 6.4 (if necessary): If your existing Delegate365 version is less than 6.5, it is necessary to re-run the Delegate365 setup once because of required app permissions to read the Office 365 service status shown on the Delegate365 dashboard. We will inform you about the planned update date and the steps to update your Delegate365 app as described in Delegate365 changelog version 6.5 and in Delegate365-(Re)run the setup.

      All existing productive Delegate365 tenants will be updated starting mid of October. New Delegate365 trials will automatically be available in the latest version.

      We hope you enjoy the new features of Delegate365! More features are about to come this year!



      Delegate365 changelog version 6.6-Mailbox features and logging

      Tuesday, September 12, 2017

      During summer time the next Delegate365 version was born that brings more mailbox and distribution group features, more sync rule options and some minor changes in logging and some fixes. See the details here.

      Delegate365 version 6.6 brings some improvements on the basis of version 6.5.

      • New sync rules: The menu administration / sync / "sync options" has been renamed to "sync rules" in Version 6.5. Now, the "user license assignments" have been extended with additional options as in the screenshot below. A sync rule can now be switched on or off with the "Active" switch to simplify testing ("On" is the default setting for existing rules). The new "order" allows to reorder the rules. "Action" now allows not only to add Office 365 licenses, but also to remove the selected licenses, which was a often requested feature. "Apply to" allows to execute the rule against "all users", "sign-in allowed" or "sign-in blocked" users. The new options deliver a much more granular control of license settings.
        image
        The active sync rules are considered at each sync operation in Delegate365. Don’t forget to save any changes at the page bottom "Save" button!
        Remember, the more rules are enabled, the longer the sync operation will run, in large Office 365 tenants this might take hours, since every object must be checked and the operations will be executed.
      • New Mailbox features: In the users list, admins can modify the mailbox settings of a user (if the admin owns permissions).
        image
        The “general” box came with version 6.5 to enable admins to hide the user from address lists.
        Below that, now there exists a new box title "mailbox features" with a bunch of switches as follows:
        image
        In here, admins can restrict the user’s access to specific features as enabling or disabling Outlook (on the web), using IMAP, POP3 or MAPI access, Litigation hold and Archiving. So, we do have much more settings to define the behavior of Exchange Online for a user’s mailbox.
        Below that, further mailbox features are available as before.
        image
      • Distribution group new features: There have been new settings added in the distribution groups.
        image
        The new “email addresses” section allows to manage multiple email addresses for one distribution group as follows.
        image
        When saving the new email alias is added to the group.
        image
        Info: In this version, this works for mail enabled security groups and distribution groups only. With the next version, support for Office 365 groups will be available as well.
      • Auditing history (reminder): We experienced, that the auditing log can become really large and that admins usually don’t need to go back for a long time frame when searching for operations. To reduce the storage and to fasten operations within Delegate365, the audit log now goes back for the last 7 days. Usually, going back a week is sufficient for a quick find of logs.
        Also, the Audit logging was changed from a single table to monthly tables. Both feature have already been introduced with Version 6.5 (pls. see Audit logging per day, Audit logging per month and Direct access to audit logs), just as a reminder.
        image
        Due to technical reasons, search works with the "startswith" operation. So, if we search for "kelly" in this scenario above (the name property is "bob kelly (tailspin)"), the entry will not be found. If we search for "bob" or "seattle", the entry will be found (lower an uppercase is ignored, leading or ending spaces are trimmed). Therefor, we recommend using the auditing module in Delegate365 just for quick lookups. If you need more detailed search, we recommend using the "reporting" module where you can get direct access to all logging data and use tools as Microsoft Excel or Power-BI or similar.
      • New Dashboard element Service health (reminder): If your tenant has not been on version 6.5 before, you need to re-run the Delegate365 setup once to enable the service health dashboard. Please look up Delegate365 changelog version 6.5-Service health, logging and more and how to Delegate365-(Re)run the setup.
      • Fixes: The Sync operation was optimized again to reduce the runtime and some minor fixes have been made in the UI.

      All existing productive Delegate365 tenants will be updated starting with mid of September. New Delegate365 trials will automatically be available in the latest version.

      We hope you enjoy the new features of Delegate365!



      Delegate365 and the Exchange issue update

      Wednesday, August 30, 2017

      In the last days, some customers of Delegate365 experienced a warning in the Delegate365 portal that informed about the failing communication to Exchange Online. This issue was caused by the Microsoft Exchange Online PowerShell endpoint. We are glad to announce that this issue should be fixed soon.

      Delegate365 informed users about the reduced functionality with a message “Access denied – please check the credentials of your Office 365 account…” when opening the yellow warning icon in the portal.

      image

      This message pops up when the Delegate365 services cannot communicate with the customer’s Office 365 tenant and the Microsoft endpoint delivers an error. The detailed error message generated by Microsoft was “…Processing data from remote server ps.outlook.com failed with the following error message: The EndpointConfiguration with the http://schemas.microsoft.com/powershell/Microsoft.Exchange identifier is not in a valid initial session state on the remote computer. Contact your Windows PowerShell administrator, or the owner or creator of the endpoint configuration. For more information, see the about_Remote_Troubleshooting Help topic.”

      At atwork we were concerned about this issue since we were using exactly this service which was working properly since years and there has been no change on our side. We started doing research, checked our code, made tests in various regions and Office 365 tenants and tried to figure out if there is any solution for the problem - with various results. In the end, we found out that the results were absolutely unpredictable and more or less random. There’s one related thread in social.technet.microsoft.com Exchange Online error: Identifier is not in a valid session state on the remote computer where we saw that more users were affected by this issue. We contacted Microsoft and continued to seek for a solution.

      Today, Microsoft announced a new status message in the service health in the Office 365 portal in many tenants:

      EX116717 - PowerShell issue: User Impact: Users may be unable to perform administrative actions when using Remote PowerShell commands.

      image

      The PowerShell issue started by Friday, 25th August 2017. The status says “Restoring service” and Microsoft expects this to be completely resolved within the next 24 hours.

      image

      The PowerShell connection issue was caused by an update that was deployed in Microsoft Office 365 Exchange systems.

      So, we hope that the Exchange PowerShell service will be working properly in all tenants again soon (in the next hours).

      On the Delegate365 side, there will be no changes. Once the service is completely available again, the next Delegate365 sync operation will update all deltas again and the warning message will be removed in the Delegate365 portal.

      Thanks to all customers for your understanding. The good news is that the services will be fixed soon and Delegate365 will work properly again!




      Delegate365-Working with License Assignments

      Thursday, June 29, 2017

      Delegate365 provides various automation tasks. One of these is the new License Assignment rule to automatically assign Office 365 licenses to users based on their user properties or on their group membership. See how this works in real world with a demo scenario here.

      The License Assignment is available since version 6.4. For details, pls. see the description here. This new feature allows to assign Office 365 licenses in a very custom way to users and runs at each Delegate365 synchronization operation, So, whenever a SyncOp runs, Delegate365 checks the sync rules and assigns licenses as specified. So let’s see how this works step-by-step as follows.

      Security Groups

      Many organizations work with security groups to simplify their user management. In my scenario, I created some security groups within Delegate365 and added some users as members. Security group Finance has Alan and Christa as members.

      image

      Security group IT has Dan as member, to keep that sample very simple.

      image

      Just to mention: In this demo, I created OU’s with the same name (Finance, IT, …) to keep the management simple. To clarify, there is no correspondence between OU’s in Delegate365 and any security groups. You can organize your tenant and your Delegate365 environment as needed.

      Existing licenses

      License tasks in Delegate365 always add licenses. This means, if a user already has a license set, this will stay untouched and new licenses will be added.

      So, here we have a specific set of license set just for user Christa: MDM, Yammer and Exchange in E3 are activated, all other license plans are disabled.

      image

      The other two users Eric and Dan do not have any licenses set.

      Sync rules

      A Portal Admin can define the sync rules in administration / sync / sync rules. Here, the User sync options are disabled, but the User license assignment will be enabled. We create a new rule where Security group contains Finance. This means, all current members of the security group Finance shall get a specific set of licenses. In our sample that’s Office Web Apps, SharePoint and Exchange in SKU E3 and additionally AAD_PREMIUM_P2.

      image

      Ok. Now we add another rule for member of the security group IT. The IT personal shall get the Skype and Teams license within the E3 SKU.

      image

      Ok. Don’t forget to Save the sync rules at the bottom of the page.

      image

      We’re done here. Since you can add many rules with various conditions, many custom scenarios can be defined.

      Optional: Don’t forget the UsageLocation

      Office 365 requires to have a UsageLocation set for each user who shall get any license. As administrator you need to take care of that fact. It can be the case, that some users have a UsageLocation set and others not. With Delegate365 this can be set in the OU Auto License Assignments if needed, in module administration / organizational units / manage ou’s (see Delegate365 changelog version 6.5-Service health, logging and more “Assign OU Licenses and UsageLocation”).

      Select the OU and click Edit licenses. In here, enable Use license auto assignment and select a country to set for UsageLocation as shown here. Usually, it’s a good idea to enable Check existing OU assignments as well to ensure that all users that are already assigned to that OU are checked for UsageLocation. No licenses are selected in here, we just want to set the UsageLocation .

      image

      The UsageLocation defined in here will only be set, if a user has NO UsageLocation set. If that user property is already set, this will be ignored (we do have the UsageLocation then already and do not need to re-assign one).

      To ensure we will also have a UsageLocation for all members of OU IT, we do the same for that OU.

      image

      Remember, this step is optional- If you are sure, all users have a UsageLocation set, you can skip this step.

      Run a sync

      Now let’s try it. We could wait for the next automatic SyncOp (which usually runs all 4 hours), or to see the result instantly, we run the SyncOp manually. This can be done in administration / sync / sync operations. Click the Sync button.

      image

      The progress box below shows the details. Depending on the size of your Office 365 tenant and your settings, this can take some minutes or even hours. In my demo tenant with just about 250 users and few groups, this takes about 3 minutes. The page must not stay open, you can continue to work in other Delegate365 pages.

      After the SyncOp has finished, you can check the result in the same page in the Sync history box. Here we see the manual triggered SyncOp.

      image

      Check the result

      Now let’s see the result in the user licenses. First, we check the licenses of Christa. We should see that she now has additional licenses in E3 (Office Web Apps and SharePoint) and AAD_Premium_P2. The existing licenses for MDM, Yammer and Exchange are set as before. So, the new licenses have been added.

      image

      The result for Eric now shows just the new licenses (MDM has been added automatically through AAD Premium by a role, this was not manually defined by us). So, we see the licenses for MDM, Office Web Apps, SharePoint and Exchange. and for AAD_Premium_P2. These licenses have been assigned since Eric is member of the security group Finance.

      image

      Let’s check user Dan who is member of IT. He got Teams and Skype as defined (plus MDM as above).

      image

      Well perfect, or?

      Stumbling stones

      As we have seen, the License Assignment is basically easy to use. But of course, it can happen, that you don’t get the desired result. If licenses are not added after a sync, the following issues can have happened:

      1. In Delegate365, there is a license quota defined for an OU and the limit is exceeded.
      2. You are out of Office 365 licenses in your tenant. Licenses could not be assigned since there are no licenses left.
      3. Licenses could not be set because of license conflicts. For example, you tried to assign the license EOP_ENTERPRISE that cannot be assigned to a user. Delegate365 tries to set the defined licenses, but if Office 365 restricts specific licenses, this license cannot be set and an error is logged (see below).

      Recommendations

      So, if something goes wrong, we recommend:

      • Check the result after a sync with some single users.
      • Check the Delegate365 error message that are collected in the notification center in the top menu bar (the message icon). Click Read all messages and see any error that may have occurred, as shown here.
        image

      ad 1) If a license quota is exceeded

      So, how does it look like if there is a license quota defined? I created another new user: Molly (without any Office 365 license in OU Finance) and added her to the Finance security group.

      image

      Then, a license quota is defined for the OU Finance with an enforced maximum of 2 licenses for SKU E3 as shown here.

      image

      After Save, we see that 2 license-quota for OU Finance.

      image

      Remember, we had already two users, Christa and Eric in that OU, with two E3 licenses. So the License Assignment for Molly should not work. We are set now, and can re-run the SyncOp (as above).

      After the SyncOp, let’s check Molly’s licenses. This looks as follows: The E3 licenses have NOT been set. You see the information “Microsoft Office 365 Plans E3 (2 of 2 used)”.

      image

      If we check the notifications, we see the reason: “No more licenses available for OU: Finance and Licenses: Microsoft Office 365 Plans E3”. The license could not be assigned because of the license quota of 2.

      image

      So, the notifications are important to check.

      If we now change the quota to, let’s say, 3 licenses and re-run the SyncOp, Molly will get the E3 license automatically. I did this and checked the result here. Molly got the E3 licenses now.

      image

      ad 2) If no more 365 licenses are available in the Office 365 tenant

      The same as described above, happens when exceeding the available Office 365 licenses of the tenant. You see the warning in the notification center.

      ad 3) If a license cannot be assigned

      Some licenses sets are not possible since they are not permitted by Office 365. For example, the message “User Licence(318) ericg@d365v6.onmicrosoft.com: License EOP_ENTERPRISE cannot be assigned to a user.” informs that that license could not be assigned. Microsoft is continuously adding licenses and plans and combinations and such messages (as for example, double license plans in different SKU’s) are possible. The notification center informs about such issues.

      Summary

      I hope this sample demonstrates the License Assignment functionality and allows you to automate your Office 365 user and license management. Check automatic license assignments after the SyncOp and see the notification center for any issues. With that toolset, it’s easy to automate license assignments. Benefit from working with Delegate365!




      Delegate365 changelog version 6.5-Service health, logging and more

      Wednesday, June 28, 2017

      Delegate365 version 6.5 is here soon. With that update, there comes new functionality and some further improvements. Read the details here.

      • Notification center: Now, the notification center shows just the last 100 messages (instead of all unread messages) to reduce the loading time for all unread messages that can be produced in a large number by the synchronization process. Anyway, you can access all messages as before by clicking the “Read all messages” link. “Clear all messages” sets all messages to “read”, so that they no longer show up in the notification center.
        image
        This step improves the dashboard’s loading time.
      • New: Hide from address lists: In the mailbox settings of a user, administrators now can hide the user’s email address from address lists by setting the Hide from address lists switch to Yes. By default, this switch is set to No. Click Save to persist that mailbox setting for the user. [Updated 29th June]
        image
      • New Dashboard element Service health: To inform Delegate365 administrators about any issues with the Office 365 services, the Delegate365 dashboard now shows the service health (and in a new menu on the left). Since this requires new permissions for accessing that data, it’s necessary to re-run the Delegate365 setup once. If the message in the new “Service health” box shows "You must run a new Setup to enable reporting. Click here to go to setup.", then click that link.
        image
        The link opens the /setup URL. You need to have the Delegate365 configuration password (you get that from atwork) and a Global Admin user of your Office 365 tenant. Fill out the three fields and click “Complete”. See Delegate365-(Re)run the setup for a step-by-step guide and more information about re-running the setup.
        After the setup, that takes about 1 minute to run, login again with the Global Admin you used in setup step 1 and confirm the Delegate365 consent with “Accept”.
        image
        As you can see, the Delegate365 app now asks for permissions to read activity, usage data and service health from your Office 365 tenant. This permission set also includes permissions for reports that will be available in the next versions of Delegate365. Then, it will not be necessary to re-run the setup since these permissions are already included. The consent is valid for all Delegate365 users in your tenant - it’s important to accept this here once. You’re done with the setup.
        Now, when entering the Delegate365 dashboard, you should see the status of the Office 365 services for your tenant. If you do not see the service status but the message “Cannot load service health.”, it can take some minutes or hours, until the new app permissions are effective in your tenant. In that case retry later by refreshing the browser window.
        The service health box on the dashboard shows the current and previous status in an overview.
        image
        The items have an icon with traffic light colors representing the functionality. In the screenshot above, there’s a warning for Exchange Online, the rest is green.You can click at the details of each service to open the service health page. The service health is also available for all admins in the left menu. In that list, click on the desired service to see the service messages. The text will be loaded and shows all messages for the last 30 days.
        image
        If there are no current messages, you can investigate for older messages with the “View history” link. Again, this loads the requested messages.
        SNAGHTML12d8b30
        ”Hide history” collapses the messages.
        SNAGHTML12f1af8
        The new service health module is available for all Administrators in Delegate365 and informs about possible issues with Office 365.
      • Renamed: Sync options to Sync rules: The sync options provide a bunch of automation. Now there can be rules defined to assign Office 365 licenses (which will be extended in near future as well). So, we decided to rename the “sync options” to “sync rules” to better describe the adapted module. The module itself got no changes in this version.
        image
      • Audit logging per day: The Delegate365 audit logging hast been changed in the past, see Delegate365 changelog version 6-Logging. Since the amount of actions can become very large, the new audit log is available per day to reduce data and improve the loading time. Before, in administration / audit / auditing, the time filter went back for 1 or more days up to 6 months. In real world, Admins usually search for specific events in the last days, so this filter now shows the last 7 days. Select the desired log (per day) first, then search or browse the audit data.
        image
        All logs older than 7 days are automatically deleted. The purpose of the daily logs is to have them accessible within Delegate365 in a quick way as shown above.
      • Audit logging per month: According the same principle to reduce data, now there is an log table for each month. When working with data exports or Power-BI, now the data size is much smaller and comes per month. The monthly logs are never deleted and are stored forever.
      • Direct access to audit logs: The internal table names now are “log201706” (for June 2017) for the monthly table and “log20170626” (for 26th June 2017) for the daily log in the Delegate365 storage and so on. See details on exporting and reporting of audit data at Delegate365-Working with Audit Logs. The “old” single table “AuditLogSearch” (which is used until the update to version 6.5) will be untouched and stays forever.
        image
        The old log files stored in the Blob containers are automatically deleted, since they were written just as backup and had no usage (cleanup). This will be discontinued in version 6.5 and there are no more Blob-files used.
      • Assign OU Licenses and UsageLocation: The automatic license assignment in the OU’s (in administration / organizational units / manage ou’s) has been slightly changed. Now the usage location can be set without the need of assigning any Office 365 license below. So, this module can now set the usage location only. In former versions, this has been ignored if no license was selected.
        image
        To clarify: the usage location is set just in case if the user not already has a usage location set. Then, the selected usage location is assigned (before the license assignment rules are executed in the SyncOp, so that they are valid for setting any Office 365 licenses).
      • Design of scripts has been optimized: The page design of the administration / sync / scripts page has been optimized to work on small screen sizes as well.
        image
        This module is currently in Beta and designed to save and execute recurring PowerShell tasks.
      • Optimizing SyncOp (License Assignments): Since there can be a bunch of different sync rules active, Delegate365 needs to check the existing user assignments and needs to execute each rule. With a large number of users and licenses, this can be time consuming and a lot of operations need to run. Delegate365 tries to reduce all read and write operations with the optimized SyncOp. The user object is read only if needed and the operations are summarized to see if an update is necessary. All in all, the optimized sync should save time (and operations against the Microsoft Graph) and run faster than before, especially in large Office 365 tenants with ten-thousands of users.

      All existing productive Delegate365 tenants will be updated starting with begin of July and in the following weeks. New Delegate365 trials will automatically be available in the latest version.

      We hope you enjoy the new features of Delegate365!




      If you want to see the full changelog, please visit our blog.