Highlighted
Intrepid explorer

FNMS On-Prem full FNMS backend installation on Azure

Jump to solution

Hello, I have a few questions regarding Azure.

Does FNMS support the On-Prem installation fully in Azure.( frond and back-end)

Are there people with experiences with a full FNMS Azure implementation?

What are the limitations? Issues/Challenges you ran in to.

I might see some challenges in Azure AD instead of Active Directory. (https://www.nhaustralia.com.au/blog/AD-DS-vs-Azure-AD-So-whats-the-difference/

 

Thanks and Regards

 

Ronald

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Flexera
Flexera

Re: FNMS On-Prem full FNMS backend installation on Azure

Jump to solution

I have several clients that are fully implemented with the "On Prem" version of FNMS deployed in public cloud - specifically Azure without issues.

The thing to keep in mind is that currently we do not support the RDS version for SQL Server - a full SQL Server (of appropriate version per the documentation) is required.

As for Azure AD - I'm not sure we've tested that integration fully - however our AD integration is in 2 main spots. First for pulling AD Information into the tool for use in various other integrations -  our Active Directory Import process. This performs LDAP queries against a domain controller. I believe binding with LDAP is fully supported with Azure AD and shouldn't be a problem. The second is that we utilize Windows Authentication in IIS for the Web Application - which should also be fully supportable. That said, I don't believe I've seen this done in the field so would want to test it....

View solution in original post

5 Replies
Highlighted
Flexera
Flexera

Re: FNMS On-Prem full FNMS backend installation on Azure

Jump to solution

I have several clients that are fully implemented with the "On Prem" version of FNMS deployed in public cloud - specifically Azure without issues.

The thing to keep in mind is that currently we do not support the RDS version for SQL Server - a full SQL Server (of appropriate version per the documentation) is required.

As for Azure AD - I'm not sure we've tested that integration fully - however our AD integration is in 2 main spots. First for pulling AD Information into the tool for use in various other integrations -  our Active Directory Import process. This performs LDAP queries against a domain controller. I believe binding with LDAP is fully supported with Azure AD and shouldn't be a problem. The second is that we utilize Windows Authentication in IIS for the Web Application - which should also be fully supportable. That said, I don't believe I've seen this done in the field so would want to test it....

View solution in original post

Highlighted
Intrepid explorer

Re: FNMS On-Prem full FNMS backend installation on Azure

Jump to solution

Hi Natalie,

Thanks for your response.

Sounds like it should be able to work in Azure.

It although sounds a bit like you are not for 100% for sure, so ill try to test it if possible.

In case you get the chance to find out more about Azure AD and the authentication please let me know!

 

Regards

 

Ronald

0 Kudos
Highlighted
Intrepid explorer

Re: FNMS On-Prem full FNMS backend installation on Azure

Jump to solution

Hi Natalie,

Today I did some more research on Azure AD and FNMS.

https://samcogan.com/azure-active-directory-is-not-active-directory/

https://docs.microsoft.com/en-us/azure/active-directory-domain-services/overview

https://youtu.be/T1Nd9APNceQ

To me it looks like the key word is : azure active-directory-domain-services that is what FNMS is depending on.

The only thing I am wondering is, what kind of detailed requirements does FNMS has for authentication and LDAP.  For example : Things like is LDAP Bind required, Does FNMS require Kerberos constrained Delegation?

It would good to know more details of what FNMS is exactly using under the engine to make FNMS work.

 

Regards

Ronald

Highlighted
Occasional contributor

Re: FNMS On-Prem full FNMS backend installation on Azure

Jump to solution

@DAWN  \ anyone,

Can you give an update on the Azure \ SQL Server aspect? It's been a year and I'm wondering if this has changed. The client is asking this and the mention SQL Server 2017 (but don't clearly say Azure SQL Server is at version 2017 - let's presume so).

Then, which of the following database options should we be using:

1.       Azure SQL Databases

   a.       Single Database

   b.       Database elastic pool

   c.       Database Server

2.       SQL Managed Instance

3.       SQL Virtual Machines

Thanks, Rob

0 Kudos