SSO and Azure/AD integration for technicians
Answered
Ability to have technicians utilize SSO from Azure/AD to sign in to the Admin Portal and additionally the ability to create technician users in the Admin Portal based on users in Azure/AD.
-
Official comment
To those of you that commented on this feature I apologize for not allowing your comments to go through and get posted. I didn't realize that they were stuck as "pending" on this board also wasn't being notified. Another partner just brought this to my attention. :-(
This feature has been planned from the inception of AutoElevate although there have been many other features in the queue ahead of it. We are now actively taking steps to work on and push this feature forward and I would anticipate the feature to arrive within Q1 of 2021.
Comment actions -
they already sold, unless passwordboss is going to be sold too
https://www.autoelevate.com/password-boss-completes-acquisition-of-autoelevate/ -
Hey guys I wanted to chime in because I know how it may seem from the outside looking in. I was an MSP for 20 years and know all too well the dread of having a solution that you like get sold and then seeing the development shelved and support go into the toilet. This is not what’s happening here at all.
AutoElevate was acquired in September of 2021 by the investment team that also acquired PasswordBoss with the plan of maintaining operations separately for a period of time with some common shared resources (HR, Payroll, Legal, etc.). The first move that was made on the AutoElevate side of the house (same day as the acquisition) was in hiring additional development staff. We were very fortunate in that we were able to steal away some superstars that our other co-founder has worked with previously and are building out the team around those all-stars.
Our whole Dev team are based in the US, are employees, and aren't simply an outsourced team from another country. This takes some time to organize. The first order of business was a complete review of all the code to get everyone up to speed and tackling some adjustments on the server, api, and database side of the equation to optimize performance and scalability. Although we haven’t changed the Agent version recently there have been numerous deployments of new code on the server, api, and database side of things which are setting the stage for the things coming next.
The acquisition (which took some significant time) and the expansion of our Dev team temporarily pushed back our original timeframes and plans but this was also done with the intent of getting all the features we have planned ultimately done much faster. We have brought on about 35 new employees in the last couple months and things are ramping up internally very quickly.
You’ll be glad to know that there are many projects cooking in Development. Here are a few of the bigger items:
- There will be a major update rolling out to which will change up the settings screen and allow additional settings but also will allow it to adhere to the hierarchy of computer/location/company/global. This will allow full customization of settings to happen down to the computer level and also for those settings to become a persistent ‘policy’. This feature is done and in the process of being documented and rolled out.
- Changes are being made to allow sub-accounts along with things that would be needed for billing of those accounts.
- Technician Mode at the Login & Locked screens
- Technician and Agent offline functionality (both Technician mode and out-of-band requests)
- WDAC (control of Microsoft’s application whitelisting) is in full swing with some significant milestones already met.
Those are the big things in motion and there are lots of other minor enhancements, features, fixes, and refinements that are also in the mix.
In regard to SSO (the reason that you all posted). I was in a Dev meeting this morning where we discussed this at length. We will be adding this into our Epics and Sprints as active development this next week and this will finally be moving forward. What the timeframe is on delivery is 'to be determined' but it is going to be moving forward because some of the other features that had to be considered in lock-step are also moving forward.
I appreciate all your patience and partnership and hope that once the features start to drop that you’ll see the value of what we’re doing and it will be worth the wait. We’ll keep you posted but in the meantime, try not to worry. Things are moving forward now at velocity that we never had before and you’ll start seeing some of the fruitage of those efforts soon. What AutoElevate is today is only the beginning we have big plans for the solution in 2022, stay tuned, and keep the faith.
-
I appreciate the update and response Todd! I’m sure others are pleased to hear that some improvements are in the pipeline as well.
Would it be possible for you and your team to get a roadmap with statuses and rollout information written up for 2022? An example of what I mean would be NinjaOne - https://www.ninjaone.com/roadmap/
This would provide some clarity and openness with the products future. And who doesn’t like getting excited reading some new features/improvements coming.
-
Hi everyone, great news! SSO with Azure AD is in early access beta right now. You can follow it's progress on our roadmap here: https://github.com/AutoElevate/roadmap/issues/1
We don't expect a long beta period, but if you would like to be added to early access (to get new features before everyone else), please email support@autoelevate.com and ask.
Additionally, we will be closing this site down as it has been replaced by our new "Roadmap" that can be found here: https://github.com/AutoElevate/roadmap#readme
You can add more feedback to proposals directly and/or subscribe to them so you can be notified of any changes to their status.
Please sign in to leave a comment.
Comments
18 comments