RELATED IDEAS
Native support for Azure Active Directory
Unfortunately NWC forces us to use Auth0/Okta as a middleware identity provider instead of offering a native Azure Active Directory connection. This puts us in a tough spot from an IT security / data privacy perspective because the Auth0 servers are located in the US and due to legal reasons we try to avoid saving data outside of Europe. Auth0 user profiles are not automatically removed once the user is (manually) de-provisioned in NWC. This is not an enterprise-ready solution I'm afraid. I would expect fully automated provisioning/de-provisioning of users (based on Azure AD groups) and a native Azure AD connection which basically became the industry standard IDP for so many companies. Maybe offer Auth0 as an option for companies without Azure, but not force everybody to go via Auth0. There should never be a chain of identity providers
This is very disappointing. Obviously I can't speak for all other European companies/customers but these IT Security / Data Privacy regulations apply to the whole continent. I can guarantee that the Octa/Auth0 dependency/requirement will not fly with the large OEM car-companies in Germany, so you will not get them as NWC customers for sure. By not pursuing an enterprise-ready option you basically ignore all of us/them and the requirements we have. This should have been something you change out of self-interest to become enterprise ready.
Thank you very much for posting your feedback for our review. At this time, we will not be adding this request to the near-term backlog, as low number of votes and we are focused on other highly requested features. However, we reevaluate requests every quarter and will reach out if priorities change. Please keep the feedback coming as it is critical for our longer-term planning.
Thanks for your feedback. Opening this up for voting.