Delegate365

As described here we are pleased to announce the new design of our D365 portal in D365 version 2.9. We completely rebuilt the design and optimized the website performance to reduce load time. We now make use of the latest Bootstrap framework and optimized all Client-side Styles and Code to reduce load time as well as using the Javascript framework AngularJS and SignalR for receiving a great website performance. The whole website now uses these technics for a good user experience with immediate response times – the user sees what´s going on, f.e. when opening a distribution list manipulating members of a distribution list or when syncing data. ...

Delegate365 version 2.9 is a new milestone in the evolution process of our Office 365 Delegation Add-On product. Have a look at the great new features: New Design We completely rebuilt the design and optimized the website performance. We now make use of the latest Bootstrap framework and optimized all Client-side Styles and Code to reduce load time as well as using the Javascript framework AngularJS and SignalR for receiving a great website performance. The whole website now uses these technics for a good user experience with immediate response times – the user sees what´s going on, f.e. when opening a distribution list manipulating members of a distribution list or when syncing data. The page setup is renewed and the menu has been cleaned up somewhat. See the details here. ...

As described here we are pleased to announce the new synchronization function in D365 version 2.9. We completely rebuilt the sync process and added rules for automatic user assignment to specific OU´s. Why Sync? Since D365 needs to deal with (ten)thousands of users in an AAD D365 uses an cache layer to deliver a good user experience and performance. So changes which are made outside of D365 - like in the Office 365 portal, via PowerShell or another App – may not be visible immediately in D365. ...

In the coming week there will be the next update of Delegate rolled out. This will be Delegate version 2.9 which includes these updates: New Synchronization: We improved the sync processes (for domains, security groups, distribution lists and user and licenses) which now are combined in one simple step. The user import now can be configured with rules for putting users in specific OU´s depending on special properties (country, security groups, AAD properties…) ...

In Delegate365 version 2.8 there´s a new setup wizard included (as announced here). With this function companies no longer need to create a (temporary) administrator user for doing the setup process of Delegate365 but instead can setup their Azure Active Directory on their own for working with Delegate365. Prerequisites To configure your real company AAD with Delegate365 you get two access information by atwork: The Setup-URL (which usually goes like https://[yourcompany].azurewebsites.net/setup) and a configuration password (which is in fact a code) to give you the access for the setup process. This code is important and valid for this specific Delegate365 appliance. With that code you can setup the service accounts till the code is changed. More about that later. ...

Next week there will Delegate version 2.8 rolled out to all appliances. There will be new features included: Setup-Wizard: There´s a new setup wizard included, so that each customer can do the configuration (and renewal of the service account) of his D365 version on his own. New Synchronization: moved to version 2.9 (updated) More to come in the next version(s)… BTW: We added the update date information and bullets in the style sheet (which was missing) in the changelog on https://delegate365.com/changelog. ...

In Delegate365 version 2.7 there were some minor fixes rolled out. Style Sheets and client messages were updated. The user import with an CSV file had a problem with updating the new imported users in the users list. Since D365 uses a cache layer for user objects to improve performance since version 2.3 the new users didn´t show up immediately after the file import but after the automatic sync task (which runs in the background in a predefined time frame). With this fix the new importet users now show up immediately in the users list. ...

Delegate365 changelog version 2.6. We internally changed the encryption of stored credentials and extended it to protect all custom values. D365 uses an own Service Account for accessing and transferring user data to Azure Active Directory. For Exchange functionality like Alias email addresses or distribution lists as well as reporting data D365 needs additional credentials. These essential data must be stored in a secure way. To ensure safety in D365 we changed the encryption and extended it to all properties stored in the D365 database with version 2.6. Now all custom config values (even fields like company name, address, phone number, etc.) are encrypted with an Advanced Encryption Standard (AES) algorithm. ...

Delegate365 changelog version 2.5. There´s a new feature concerning distribution lists built in. We got the request that it would be useful to integrate existing distribution lists into other distribution lists (DL) in D365, so that all members of a DL automatically receive emails if their DL is member of one or more other DL(´s). So now in D365 v2.5 it is possible to put existing DL´s as member into another DL. This feature is handy and reduces potential synchronization steps and eases the organizational tasks for the admins. ...

Delegate365 changelog version 2.4. We optimized some changes in the SMS notification service. New feature SMS-notification. Each customer can define if he wants to use SMS notifications in D365 or not. With SMS there are additional costs for the SMS provider. To ensure that a customer is aware of that function we can completely switch the SMS sending on or off. Admins: If yes, admins can define if they want to receive a notification via email and/or SMS: When editing the admin you can define each channel: email and/or SMS. The format of the phone number must be like this sample: ...