Get started

FoxIDs is available at or you can deploy FoxIDs in your Microsoft Azure tenant as your own private cloud. is deployed in Europe in Microsoft Azure Holland as an Identity Services (IDS) also called Identity as a Service (IDaaS).

  1. Register on, where you get access to your one FoxIDs tenant. The tenant will hold your organizations entire security service.
    You become the first admin user and you can add more admin users later on. You can optionally configure external trust in the master environment to authorize external admin users.

FoxIDs Private Cloud

You can deploy FoxIDs as your own private cloud in your Microsoft Azure tenant.

  1. Deploy FoxIDs in your Microsoft Azure tenant.
  2. After successfully deployment, login to the master tenant.
    You can create more admin users in the master tenant. You can optionally configure external trust to authorize external admin users.
  3. Create the tenant for your organizations security services. Applications, APIs and connections in general is configured in this tenant.
    You can create more admin users in the new tenants master environment. You can optionally connect the master tenants master environment to the new tenants master environment to authorize admin users from the master tenant.

1) First login

You are presented with a list of your environments when you login.

FoxIDs first login

The default environments in a tenant:

  • master is the environment responsible for access to the tenant and the subsequently environments.
    The Control Client and Control API is configured in the master environment and admin users is added to the master environment. You should normally not add applications in the master environment.
  • - (dash) is the production environment holding your organizations production security service
  • test is a environment meant for testing. You probably need more environments for dev, test QA etc.

You can add and delete environments as you wish including deleting the default - (dash) and test tasks.

2) Run the first application

You can e.g. start by configuring the first application in the test environment, add test user(s) and login.

You can either configure your own application or configure the samples and run a sample application.

Add a test user to be able to login!

Add test user(s)

Select the test environment and go to the Users tab to create a test user(s).

Test user

Then click Create User, fill out the page and click Create.

Create test user

Default login UI

In the test environment go to the Authentication methods tab where you find the default login authentication method which handles the user login and logout.

Login authentication method

Configure your own application

In the test environment go to the Applications tab to configure your application.

A web based applications (client / relaying party) can be configured with OpenID Connect or SAML 2.0.

Application registration

It is possible to add more authentication methods to federate with external Identity Providers (IdPs). Thereafter, a new authentication method can be added to your application registration.

Sample application

The sample applications can be found in the samples repository.

The samples contains a configuration seed tool which is used to configure all the samples in the test environment or another environment.

After successfully configuring the samples a good starting point is the AspNetCoreOidcAuthCodeAllUpPartiesSample web application.
You need to update the tenant and environment configuration in the appsettings.json config file and thereafter the sample should work.