Click here if you like to subscribe the ChangeLog as an RSS feed.
Thursday, April 14, 2022
Exchange Online message tracking logs can be searched by sender or recipient email address to find specific email messages. This update improves the speed of the runtime behavior of the message trace function in Delegate365.
All existing Delegate365 versions v9.2.5 have been already updated with this version. No interaction is required on the part of the customer. All minor versions will be updated this month in consultation with customers.
Monday, March 28, 2022
When using Delegate365, the system sends emails for various notifications. If the email is not received, check this configuration.
Check these relevant points:
We hope this quick overview helps. For more troubleshooting tips, see Troubleshooting Delegate365 - Why does Delegate365 not show users?
Thursday, February 17, 2022
Delegate365 v9.2.5 got another update: The license ordering module can display a custom file to provide additional ordering information for administrators when requesting new licenses.
This option supports administrators in their ordering process and can provide company-specific information about the order. The document is then displayed with a link in the license ordering module.
We think this simple method will help admins to appropriately describe the ordering process for their organization. All existing Delegate365 versions v9.2.4 and v9.2.5 will be updated with this version in the next days. No interaction is required on the part of the customer.
Wednesday, February 9, 2022
With this update, Delegate365 allows viewing and changing licenses for shared mailboxes and resource mailboxes. Since each mailbox is a user mailbox and Delegate365 works with the OU scopes, the behavior of the new license management depends on the assigned OUs and objects. Details can be found here.
The modules Mailboxes / Shared mailboxes and Mailboxes / Resources now show a module Licenses in the context menu on the right when a mailbox is selected in the list.
The Licenses menu is always visible. But, there can be some scenarios regarding the behavior of that men. In the following we show examples of this.
Here, Adele is a scope admin, responsible for 2 OUs, New York and London. The Admin, with the portal admin role, has access to New York, London and Seattle.
Also, the Admin has created license quotas for all OUs. London has a quota of 5 x Office 365 E3 licenses, and New York and Seattle have a quota of 10 x Office 365 E3 licenses.
Here, Adele is a Scope Admin, responsible for 2 OUs, New York and London. She created a new Shared Mailbox Shared1 in Delegate365, assigned to London. When Adele opens the Licenses menu, she can view the licenses that are assigned to Shared1, but she cannot modify the licenses. A message says: "Assign License. This mailbox licenses cannot be changed because the user mailbox is unassigned in Delegate365. Please contact your administrator to assign the relevant user to an OU that you can manage."
The reason lies in the technical and licensing model of Microsoft 365: Each mailbox is a user mailbox, and a license can only be assigned to the user mailbox.
In this case, a shared mailbox has been created, but the user mailbox is not assigned to an OU in Delegate365. Therefore, any license quotas would not work because the user license is missing in the model.
Solution: An admin should assign the user mailbox to an OU in Delegate365 that the scope admin Adele can manage. In this sample, the Admin manually assigns the user Shared1 to OU London (which Adele can manage). See the required steps here.
This is it. The Shared1 user mailbox is now visible in the Delegate365 Users list and assigned to OU London. Now the behavior is as follows.
Back to our scope admin Adele: When she opens the Licenses menu for Shared1, she now can fully manage the Microsoft 365 licenses for that mailbox. She assigns 1 Office 365 E3 license, as here.
A notification is shown with the operation result:
Note: The assigned license counts against the defined quota of London. Now, there´s 1 Office 365 E3 license used out of 5 available licenses. Also, Adele sees the user mailbox Shared1 in the Users module.
Solution + recommendation: This is the desired setup. Admins should assure that user mailboxes are assigned to an OU in Delegate365, manually or automatically.
The third scenario is, if a user mailbox is assigned to an OU, but the scope admin can not manage that OU. Here, the user mailbox Shared2 is assigned to OU Seattle, but Adele has only access to OU New York and London. The Admin assigns Shared2 to Seattle.
When we remember, Adele created Shared2 and assigned the shared mailbox to London. So, the user mailbox Shared2 is assigned to Seattle, but the shared mailbox is assigned to London…
When Adele opens the Licenses menu, the licenses can be viewed, and she gets the following message: "Assign License. The user mailbox is assigned to OU Seattle. Therefore, the licenses cannot be changed because the user mailbox is assigned to an OU that you are not allowed to manage. Please contact an administrator who can manage the user mailbox in the corresponding OU."
In this case, Shared2 has no Office 365 E3 license assigned, but other M365 licenses are assigned. Assigned licenses count against any quota in the user mailbox corresponding OU, here it´s Seattle. Adele can view the licenses, but she cannot modify them.
To clarify, if an Admin now assigns an Office 365 E3 license to Shared2 in the user´s module, this license is counting for OU Seattle. Then, there is 1 out of 10 licenses used in Seattle, as shown here.
If Adele now checks Shared2 in the Shared Mailboxes module, she sees the assigned license with the quotas of Seattle (1/10). Again, she has no access to modify that mailbox license in Seattle, as here.
Solution: An admin should assign the user mailbox to an OU in Delegate365 that the scope admin Adele can manage, as in case 1. In this sample, the Admin manually assigns the user Shared1 to OU London (which Adele can manage). See the required steps here.
In the Users module, the Admin selects Shared2 and opens the Switch OU menu.
The OU is changed from Seattle to London.
When this is done by the Admin, Adele can now fully manage the Shared2 mailbox license. Also, the license counts against the quota of London (1/5).
If admins don't want their scope admins to be able to manage licenses in shared mailboxes and resource mailboxes, they should be removed as a user from the OU, as here.
Then, Scope Admins as Adele can (always) view assigned licenses, but they can not modify them. In this case, assigned licenses do NOT count against any OU quota in Delegate365 (as you can see, the quota shows the number of available licenses in the M365 tenant, here 2 for E3, and not the E3 quota of 5 for London or 10 for Seattle).
This is the default behavior, as described in Case 1.
This update will be deployed to all Delegate365 v9.2.4 and v9.2.5 tenants automatically in the next days. In case of any questions, pls. contact us.
Monday, February 7, 2022
Delegate365 v9.2.5 includes a new module showing a user´s authentication methods and the assigned devices. See the details here.
This update will be deployed to all Delegate365 v9.2.4 tenants automatically in the next days. For Delegate365 tenants with previous versions (less than v9.2.4), this version will be deployed with the next update. In this case, a setup by the Admin is required once to enable Delegate365 to access this feature. In case of any questions, pls. contact us.
Wednesday, January 19, 2022
Delegate365 v9.2.4 is the latest update that brings new service health, guest user information, teams templates and other improvements. See the details here.
This version will be updated in all Delegate365 tenants over the next month. New Delegate365 tenants will automatically get the latest version.
Tuesday, January 18, 2022
In Delegate365, a new Microsoft Team can be deployed using a teams template. Teams can also be cloned. Details can be found here.
The new Teams capabilities provide more options for managing Microsoft Teams for your OUs and for the organization. More new features in this update are available at Delegate365 changelog 9.2.4-Service health, guests, and teams templates.
Wednesday, December 8, 2021
Microsoft announced the retirement of the Microsoft Service Communications API (Msg MC299902). Therefore, we changed the service health components in Delegate365 to use the successor API functions with immediate effect and to get more data. A new setup of Delegate365 is required. See the details here.
The Service health module in Delegate365 shows, what´s happening in a specific Microsoft 365 tenant at a glance to all authorized users. Contrary to the required authorizations in M365, this is not necessary in Delegate365. All admins can view the service health and the message center posts.
With this update, this module changed.
Since the old Service health API will be deactivated on December 17th, 2021, it is required for a Delegate365 Admin to renew the Delegate365 app and to consent to the new required permissions as a global administrator. Pls. see the article Run the Delegate365 setup and follow the steps.
All Delegate365 tenants will be upgraded to the new version this December.
Wednesday, September 8, 2021
In some tenants, sometimes reports appear blank. This can happen when reports are obfuscated in the Microsoft 365 admin center. See more here.
Reports can be scheduled and downloaded in the Reports menu. When the report generation is completed, they show up in the list, as here.
When the report is open and "no data available" is displayed (although you see users and groups in the Delegate365 pages)…
…the reason will likely be that Microsoft 365 obfuscates user, group and site data in the report settings. In this case, as administrator, check as Admin Center / Settings / Org Settings / Reports settings (Microsoft 365 admin center), as here. Note that in new tenants this feature can be set to On by default.
While it may be understandable to activate this "report obfuscation" feature for reasons of security and compliance, it results in Delegate365 receiving no data and displaying empty reports when users, groups or SharePoint sites are included. M365 then only delivers Id´s that cannot be mapped to a user that is assigned to an OU in Delegate365.
If your organization's compliance guidelines allow, disable this report setting in your M365 tenant to view report data.
As a result, data will appear again in Delegeate365 in newly created reports. You can find a list and samples of all available reports in Delegate365 here.
Monday, July 26, 2021
Delegate365 v9.2.3 brings a fix for the Message Trace function and offers a mechanism to add multiple users to one or more groups directly from the user list. See it here.
This version has already been updated in all Delegate365 tenants and is available as of today.
If you want to see the full changelog, please visit our blog.