Azure AD Automatic User Provisioning
Respondida
Enable the ability to automate the addition and remove of users via the Azure AD Service.
I am able to do this with my other Web Applications and it is a huge benefit, and greatly streamlines the new user onboarding process.
Here is the documentation regarding the feature.
https://docs.microsoft.com/en-us/azure/active-directory/active-directory-saas-app-provisioning
-
Hi Luke,
Thank you for your input. We've reported your feature request to our Development Team for review.
I see that you've opened a support ticket regarding this matter, they'll be able to assist you if you have any questions. We appreciate your feedback!
Thanks again,
Lauren
KnowBe4 -
Great news! You now have the capability to use our Active Directory Integration (ADI) with Azure Active Directory Domain Services!
You can sync your Azure Active Directory users and groups to your KnowBe4 console! See our ADI and Azure AD Domain Services article for more information.
-
This does not address what the original poster requested. This new feature only helps in cases where customers are hosting AD Services in Azure and not on-prem.
The poster is requesting that you implement built-in support for Azure provisioning and SSO as mentioned in this article - https://docs.microsoft.com/en-us/azure/active-directory/active-directory-saas-app-provisioning%C2%A0. This eliminates the need to stand up a new server and/or to install anything at all in the customer's environment. Just a few clicks and everything is setup.
All the big players have started doing this.
-
Hi Nick!
Thank you for the clarification toward the original post, and in your own request. I've submitted your request directly to our Product and Development teams for review. While I can’t provide a timeline or guarantee that this feature request will be implemented, we certainly take customer feedback into consideration when planning future developments.
Thanks again!
Lauren
KnowBe4 -
Hello Jason,
Thank you for posting to the community board about AD Azure SCM provisioning, I agree that this would be a useful tool for those utilizing Azure AD and I've added you to the feature request on the matter.
Our Dev team takes these requests seriously and is very interested in implementing enhancements for our users. While I can't provide a timeframe or guarantee on this implementation I will say that our Dev team takes these requests seriously and is very interested in adding these enhancements for our users.
Thank you for your submission, let us know if you have any other suggestions we could get to our dev team.
-
Hi KB4 Team!
1. Can we mark this Incomplete or Pending or anything other than Completed? The request is different from the solution that was posted.
2. I want to up-vote this request, times are changing and Azure AD and other IDP tools are coming in fast... I'm sure you know the competitors have it and it is a factor to consider during the decision making.
Hopefully we can get an ETA soon!
Thanks,
jerome
-
Hello Justin and Jerome!
I've changed the status of the post to Answered and not Completed so that we can continue to follow the upvotes associated. I'll also get your requests over to the dev department so that they know that this is a factor when choosing a training/ phishing platform.
I'm positive that our Dev team is always looking for ways to make user provisioning better for our customer base and full provisioning via Azure AD would be a great feature!
Thank you all for contributing and upvoting this popular post!
-
As a cloud-forward business using Azure AD for identity management rather than on-prem AD, having SCIM provisioning available is very important for us. Currently I need to manually provision and deprovision on every change to our workforce, and this adds a significant workload. Setting up Azure AD Domain Services just to allow automatic provisioning with KnowBe4 is a cost we cannot take on.
-
Also adding my voice for this request. It takes a huge burden out of user management by having a standardized method (SCIM) for importing users via a cloud service. I've had to create three separate connectors for the domains under management and I spend way more time than I should just making sure its accurate.
-
I just wanted to add my support for this feature request.
We have 2 AD domains in 2 separate forests. We currently use the KnowBe4 ADISync tool for one domain and the CSV import for the other.
Originally, we tried getting the ADISync tool to work with both domains, but it appeared to be a limitation.
I believe adding the user provisioning via Azure AD sync would resolve this issue for us as well.
-
Hi Matthew,
Welcome to the community board. Thank you for contributing to the post. I can definitely see how this would be beneficial to your organization.
Thanks for taking the time to pass along this feedback, our team really appreciates it! At this time I have gone through and sent a request directly to our development team for further consideration. While I can’t provide a timeline or guarantee that this feature request will be implemented, our team always appreciates this information.
-
As a new customer I've spent a while trying to work out how best to sync our AAD users. It seems this isn't available!
Sure I can sync the local AD but we don't have all out users in the local AD, some are cloud only. The same as Matthew above, we also have multiple AD domains (both synced to the same AAD directory). The one thing all our various group companies are converging on is the use of AAD as an authentication and user management service.
For us it would make perfect sense to allow direct sync with AAD. Please make this happen KnowBe4. Thanks.
-
I want to add my support for needing a proper SCIM provisioning integration as well. Legacy (on-prem) Active Directory is a dying technology, and requiring Azure ADDS is not a valid work-around, especially for more modern enterprises leveraging Okta and other SaaS identity providers.
Having a proper SCIM provisioning API would unlock potential for KB4 customers using pretty much any modern identity provider (including Azure AD natively).
Por favor, entrar para comentar.
Comentários
76 comentários