blog.atwork.at

With the many new functions in the latest version, Delegate365 has received even more updates in version 9.1. See more new features such as the new user sync property StateOrProvince, the notification license names lookups and logs and guest user modifications here.

See an overview of all updates at Delegate365 changelog 9.1-many new features. The following features have been added to Delegate365 v9.1 including all existing versions:

• New user sync property StateOrProvince: In Administration / Sync rules, in the User section, there is a new property StateOrProvince available. This new property allows that all users with an OU name in that user property can be automatically assigned to the OU, in the same way as with the other user properties.
  
  Note: In general, it is recommended to use the Sync with security group feature from an organizational perspective if possible. See more at Sync with Security Group.
• New: Notifications include Licenses names: When licenses are assigned (manually or automatically), license errors can occur. Delegate365 informs about such errors and logs them. For example, if there are no more licenses in the pool or if the quota is exceeded, a warning is created in the Delegate365 notification center. Unfortunately, the Office 365 API only delivers a message with the ID of the SKU, but no licenses name, such as:
  

  UserLicenseSyncJob(349) ChristieC@M365x836814.onmicrosoft.com: 
  Code: Request_BadRequest Message: 
  Subscription with SKU c7df2760-2c81-4ef7-b578-5b5392b571df does not have any available licenses.
  Inner error: AdditionalData: request-id: 07c100b3-9e70-409e-8a38-66b1517573c1 
  date: 2020-03-30T07:31:00 ClientRequestId: 07c100b3-9e70-409e-8a38-66b1517573c1

  To make more sense, Delegate365 now completes such messages and adds the Office 365 licenses name, and if used, the Delegate365 friendly license name after the SKU ID.
  

  UserLicenseSyncJob(349) ChristieC@M365x836814.onmicrosoft.com: 
  Code: Request_BadRequest Message: 
  Subscription with SKU c7df2760-2c81-4ef7-b578-5b5392b571df (OFFICE 365 ENTERPRISE E5) (Enterprise E5) does not have any available licenses.
  Inner error: AdditionalData: request-id: 07c100b3-9e70-409e-8a38-66b1517573c1 
  date: 2020-03-30T07:31:00 ClientRequestId: 07c100b3-9e70-409e-8a38-66b1517573c1

  In the sample above, the "Office 365 Enterprise E5" license (with the friendly name "Enterprise E5") could not be assigned to user "ChristieC" because there are no licenses left in the Office 365 tenant. The same completion happens for other license-related messages containing an Office 365 license ID. Another example with excluding license assignments, when a license shall be set, but another license is already assigned:
  

  License assignment failed because service plans afc06cb0-b4f4-4473-8286-d644f70d8faf (Skype for Business Online (Plan 1)),0feaeb32-d00e-4d66-bd5a-43b5b83db82c (Skype for Business Online (Plan 2)) are mutually exclusive, service plans 4a82b400-a79f-41a4-b4e2-e94f5787b113 (Exchange Online Kiosk),efb87545-963c-4e0d-99df-69c6916d9eb0 (Exchange Online (Plan 2)) are mutually exclusive.

  Here, the Skype for Business Online (Plan 1) cannot be assigned if Skype for Business Online (Plan 2) is already assigned to a user or vice versa. To handle thousands of such possible messages in large tenants, the license name completion happens automatically in the background within some minutes. It can take up to five minutes till the completed messages show up in the notification center in the top menu bar as shown here.
  
  We think this update makes a lot of sense to make such errors more readable for administrators.

• New notifications log: The notifications that are shown in the Delegate365 notification center are now logged extra to the Delegate365 log storage. Here Delegate365 works on the same principle: The prefix of the tables is named "notification", followed with the year, month and day. Messages are saved daily for the last 7 days (notification20200330), in a monthly log (notification202003), per year (notification2020) and overall (notificationLog). The messages are the same as in the notification center shown above. The Microsoft Storage Explorer helps to access the data directly.
  
  This allows admins to work with the notification log data in other systems easily. See more at Working with Audit Logs.
• Guest UPN: New behavior when editing guest users: In Azure AD, guest users are stored with a "special" UPN. "some.user@somedomain.org" is stored as "some.user_somedomain.org#EXT#". For such users, Delegate365 now allows to leave the UPN unchanged when setting the first name, last name and the display name. The UPN remains and is not generated automatically from the name fields for guest users. Alternatively, administrators can set a new UPN without #EXT# if desired. "@domain.ext" is controlled by the Domain dropdown below and is added automatically.
  
  Note: The login for guest users works as before, with their email address they used when registering. The UPN is just the Azure AD "internal" name that can be set to a more user friendly name in Delegate365. This is a feature of Delegate365 only. Changing the UPN to another name is not available in the Office 365 Admin portal or in the Azure portal.
  In this sample, the UPN of that guest is set to tonipohl43_gmail@M365x836814.onmicrosoft.com (without the ".com#EXT#" text). "@domain.ext" is added automatically.
  Note: Don´t add a "@" in the UPN because that would result in 2 times "@" in the UPN, such as tonipohl43@gmail@M365x836814.onmicrosoft.com and that would not be valid.
  
  This Delegate365 feature allows to leave the UPN of guest users unchanged (...#EXT#), or to change the UPN without this format if desired.

This update was carried out automatically in all existing Delegate365 versions 9.1 and is included in all new versions as well. We hope to support many administrators with the new features.