Release Date
17th April 2020
Purpose
This is a minor maintenance release that carries a number of fixes and minor enhancements, mainly to the Microsoft Online Services components.
Features
REF |
Description |
1437 |
Update Exchange Refresh Token during sync Exchange Online token will now be refreshed in the same way as the Partner Refresh Token. This will mean that the token doesn’t have to be manually renewed every 90 days. |
1417 |
Change the primary domain for MSOL in Atria when federating a certain domain A new feature has been introduced to allow the management of the default domain through the Azure AD service UI. There is now a new column to select a domain as ‘default’. Note there are two cases where you will not be able to select the domain – if it is not verified or if it is set as read-only. |
Fixes
REF |
Type |
Description |
|
|
|
1515 |
Defect
|
X500 Addresses are causing sync failures Azure AD Sync process fails when users in Azure AD have X500 addresses assigned to their proxyaddresses. Sync process has improved and will now only sync smtp or SMTP aliases. Users with X500 (or other) addresses can now be successfully synchronised into Atria without error. |
1511 |
Defect
|
AzureAD and MSOL fails on Customer Move action Moving a customer that has Azure AD and MSOL into a different reseller or location through the customer move process results in an error. This has now been fixed and the customer move action can be used to move customer to a different reseller or location. |
1517 |
Defect
|
User synchronisation fails for users with no firstname or lastname An issue occurs when the user does not have first name and last name fields in Azure AD, this has now been addressed and the default values for these fields remain in atria. |
1557 |
Defect |
MSOL Atria Plans changed by Sync process are not appearing in Billing reports When customer licenses are changed outside of Atria, the sync process cannot detect the changes and update the impacted users so they have the correct licenses assigned. This has now been fixed. |
1531 |
Defect |
Incorrect result from Microsoft GraphAPI used for License assignments The response from graph API is now cross-referenced against another call to ensure that phantom licenses get ignored by Atria. |
1545 |
Defect |
Service Import Order deletes rules incorrectly A fix has been added to remove this behavior. Due to known constraints, the Azure AD service should still be imported before the MSOL service. |
1555 |
Defect |
Additional logging for MSOL Sync Additional logging features have been introduced for Microsoft Online and Azure AD. This includes the addition of a correlationId so logs can be grouped by request. correlationId has been introduced for MSOL at this stage but will be implemented right across the stack in the future. correlationId ends up in the LogEvent column of Events table. You can now track the event logs in order simply by running a query like SELECT * FROM LOGS WHERE LogEvent LIKE ‘%0000-0000-0000-0000-000000000000%’ ORDER BY Id Desc |
Deployment/Update Checklist
The following Atria components need to be updated, follow the recommended order of update.
Components to deploy:
Step |
Component |
Command line |
Service |
Completed |
1 |
AtriaWeb 12.6.6.118 |
choco install atriaweb |
Platform |
|
2 |
AtriaProvisioning 12.6.6.118 |
choco install atriaprovisioning |
Platform |
|
3 |
AtriaAzureAD 12.6.6.118 |
choco install atriaazuread |
AzureAD / MSOL |
|
4 |
AtriaMsol 12.6.6.118 |
choco install atriamsol |
AzureAD / MSOL |
|
5 |
AtriaMsolWS 12.6.6.118 |
choco install atriamsolws |
AzureAD / MSOL |
|
Note it is important to execute atriaazuread prior to atriamsol to avoid the possibility of rules being incorrectly removed.
Recent Comments