# Fortytwo Docs > Documentation and user guides for Fortytwo products and managed services: AI Universe, Identity Universe, managed Entra ID services, Azure Marketplace offerings and reference architectures. Fortytwo: We Build Intelligent Companies. The full text of every page is in https://docs.fortytwo.io/llms-full.txt. ## AI Universe Your own AI platform, running in your Azure tenant. Build, govern and run AI apps. - [AI Universe](https://docs.fortytwo.io/ai-universe/): Your organisation's own AI platform. It runs in your Azure tenant, under your rules, and lets every team build the AI apps they need. - [How it works](https://docs.fortytwo.io/ai-universe/how-it-works/): One deployment per organisation, entirely inside your own Azure subscription. Here is what it is made of and how a question reaches a model. - [Before you install](https://docs.fortytwo.io/ai-universe/get-started/before-you-install/): What you need in Azure, Entra ID and DNS before AI Universe can be installed in your tenant. - [Install AI Universe](https://docs.fortytwo.io/ai-universe/get-started/install/): Run the installer once to set up AI Universe in your subscription. After that, everything happens in the control panel. - [First sign-in](https://docs.fortytwo.io/ai-universe/get-started/first-sign-in/): Sign in to the control panel for the first time and let the setup guide get the platform ready for its first app. - [Connect GitHub](https://docs.fortytwo.io/ai-universe/get-started/connect-github/): Every app lives in its own GitHub repository. The setup guide connects the platform to your GitHub organisation in four short steps. - [Create an app](https://docs.fortytwo.io/ai-universe/apps/create-an-app/): Name it, say what it should do, answer four compliance questions. The platform sets up the repository, the cloud resources, sign-in and the AI in about a minute. - [Agents](https://docs.fortytwo.io/ai-universe/apps/agents/): Every app has an agent, the AI your people talk to. Brief it in plain words, decide what it may do, and try it before anyone else does. - [Wisdom](https://docs.fortytwo.io/ai-universe/apps/wisdom/): Wisdom is what your teams' AI coding assistants follow while they build apps. Write your house rules once, and every app picks them up. - [People in an app](https://docs.fortytwo.io/ai-universe/apps/people/): Each app has its own list of people. Giving someone access to an app gives them that app and nothing else. - [Build](https://docs.fortytwo.io/ai-universe/apps/build/): Two ways to change an app, both working on the same code. In your browser with Studio, or in the coding tool you already use. - [App settings](https://docs.fortytwo.io/ai-universe/apps/app-settings/): An app's own settings. Its details and owner, model and agent, keys, size, cost, logs, compliance entry, and removing it. - [Home](https://docs.fortytwo.io/ai-universe/control-panel/home/): The control panel home shows what needs you, how much AI is being used, and your apps at a glance. - [AI and models](https://docs.fortytwo.io/ai-universe/control-panel/ai/): Choose which AI models your agents may use, set the safety rules every question and reply passes through, and pause all AI with one switch. - [People in the control panel](https://docs.fortytwo.io/ai-universe/control-panel/people/): Who can sign in to the control panel, what they may do there, and who may create apps. - [Settings](https://docs.fortytwo.io/ai-universe/control-panel/settings/): The platform's own settings. This deployment, the platform features, the technical pages IT needs, and your account. - [Security and data](https://docs.fortytwo.io/ai-universe/governance/security-and-data/): Where your data lives, who can reach it, and how every AI call is governed. For security reviews and data protection officers. - [Cost](https://docs.fortytwo.io/ai-universe/governance/cost/): What AI is costing you, where it goes, and what it was spent on, per day and per app. - [Compliance](https://docs.fortytwo.io/ai-universe/governance/compliance/): Your AI system register, a tamper-evident change log, and an evidence pack for auditors under the EU AI Act. - [Vulnerabilities](https://docs.fortytwo.io/ai-universe/governance/vulnerabilities/): Every app is scanned for known vulnerabilities once a day. See what needs fixing, who should fix it, and what is already on its way. - [Upgrades](https://docs.fortytwo.io/ai-universe/operations/upgrades/): Upgrade the platform to a new release from the control panel. It plans the upgrade, you approve it, and it runs inside your tenant. - [Support](https://docs.fortytwo.io/ai-universe/operations/support/): Health checks, repair actions and support bundles in the control panel, and how to reach Fortytwo. - [Words we use](https://docs.fortytwo.io/ai-universe/operations/glossary/): The words AI Universe uses, and what they mean. ## CheckID Onboard new employees with an ID they already trust, such as BankID, and no temporary passwords. - [CheckID](https://docs.fortytwo.io/checkid/): CheckID lets new employees sign in for the first time with an identity provider they already use, such as BankID, and get their Microsoft Entra ID account without temporary passwords. - [What is CheckID?](https://docs.fortytwo.io/checkid/get-started/what-is-checkid/): CheckID helps organizations onboard users into Microsoft Entra ID securely, quickly, and with less IT overhead. - [End-user walkthrough](https://docs.fortytwo.io/checkid/get-started/end-user-walkthrough/): What a new employee sees when they set up their account with CheckID, from verifying their identity to signing in with Microsoft Authenticator. - [User Journey with technical details](https://docs.fortytwo.io/checkid/get-started/how-the-flow-works/): The user opens the CheckID page and chooses which identity provider to sign in with. - [Configure Consent and Entra ID Settings](https://docs.fortytwo.io/checkid/onboarding/first-time-setup/): To allow CheckID to function correctly, you'll need to configure a few settings in Microsoft Entra ID. - [Getting started - Phishing resistant](https://docs.fortytwo.io/checkid/onboarding/phishing-resistant-setup/): This configuration is the most secure way of configuring Entra ID, where your users are all required to authenticate using Phishing-Resistant authentication. - [Identity providers](https://docs.fortytwo.io/checkid/onboarding/identity-providers/): The identity providers CheckID currently supports, with the countries they cover and their security level. - [Passkey Supported Devices](https://docs.fortytwo.io/checkid/onboarding/passkey-supported-devices/): Passkeys are supported on modern phones, tablets and computers with a recent operating system. - [Custom Domain Setup](https://docs.fortytwo.io/checkid/customise/custom-domain/): Use your own domain with CheckID, such as onboarding.yourcompany.com, by setting up a simple DNS record. - [Custom Branding](https://docs.fortytwo.io/checkid/customise/custom-branding/): CheckID supports custom branding, managed by our CheckID team. - [Supported Languages and Locales](https://docs.fortytwo.io/checkid/customise/languages-and-locales/): The languages and browser locales CheckID supports, and how the default language is used. - [Custom Security Attributes](https://docs.fortytwo.io/checkid/identity-data/custom-security-attributes/): CheckID recommends storing national identity numbers (NINs) in Entra ID in Custom Security Attributes (CSA), which are only readable by users and service principals that have been explicitly granted access. - [Time Stamping](https://docs.fortytwo.io/checkid/identity-data/time-stamping/): Time stamping is an optional feature that allows for a timestamp to be emitted and written to a custom security attribute every time an account is claimed via CheckID. - [Custom Password Blacklist](https://docs.fortytwo.io/checkid/identity-data/password-blacklist/): CheckID supports custom password blacklists, allowing organisations to prevent the use of weak, predictable, or organisation-specific passwords during password creation or reset. - [Password Agent Installation Guide](https://docs.fortytwo.io/checkid/identity-data/password-agent/): The CheckID password agent listens for change password requests from CheckID, executes the password change in the local Active Directory (AD) and reports back the status of the password change. - [Authentication Strengths](https://docs.fortytwo.io/checkid/conditional-access/authentication-strength/): A Temporary Access Pass will not be able to satisfy policies requiring Passwordless MFA or Phishing-resistant MFA, and the onboarding will fail. - [Require Approved or Protected App Policy](https://docs.fortytwo.io/checkid/conditional-access/approved-or-protected-app/): If you have a conditional access policy that always require compliant device, you will run into issues where the user cannot register a passkey during onboarding. - [Onboarding Group](https://docs.fortytwo.io/checkid/conditional-access/onboarding-group/): CheckID supports temporarily adding the user that is onboarding to an Entra ID security group that can be used for the purpose of excluding the onboarding user from a conditional access policy. - [Release Notes](https://docs.fortytwo.io/checkid/release-notes/change-log/): For the latest CheckID product updates, improvements and fixes, visit the CheckID Changelog. - [Account Setup confirms your sign-in method before completion](https://docs.fortytwo.io/checkid/release-notes/account-setup-check/): Users can now only finish account setup in CheckID once a supported sign-in method is ready on their account. - [Frequently Asked Questions](https://docs.fortytwo.io/checkid/release-notes/faq/): Answers to common questions about how CheckID secures customer environments, handles PII, controls access and notifies customers of incidents. ## Identity Universe Identity and access management built on the data you already have about your people. - [Identity Universe](https://docs.fortytwo.io/identity-universe/): Identity Universe is Fortytwo's identity and access management platform. It takes the data your organisation already keeps about its people — in HR… - [Getting started](https://docs.fortytwo.io/identity-universe/getting-started/): Go here to access Fortytwo Identity Universe: https://universe.fortytwo.io - [Permissions](https://docs.fortytwo.io/identity-universe/getting-started/permissions/): We have to assign permissions to administrators and users for them to be able to access the portal. - [IAM Core](https://docs.fortytwo.io/identity-universe/iam-core/): The IAM Core, is the heart of the Identity Universe, and is what makes most of the revolving services run. The IAM Core is populated by adding data… - [Getting started](https://docs.fortytwo.io/identity-universe/iam-core/getting-started/): Consent has to be granted by a Global Administrator, once per tenant. See getting started for details, and Administrator permissions for the roles that… - [Connectors](https://docs.fortytwo.io/identity-universe/iam-core/connectors/): Connectors are one of the most essential part of IAM Core, as it is the only way for data to flow into it. There is no way to modify a core object without… - [Alexis HR (Simployer)](https://docs.fortytwo.io/identity-universe/iam-core/connectors/alexishr/): A first party connector that imports people and organizational data from Alexis HR. - [Demo data - HR](https://docs.fortytwo.io/identity-universe/iam-core/connectors/demodatahr/): There are two dedicated demo data connectors for a non-existing Norwegian municipality named Utkanten Kommune. This connector provides HR data and the… - [Demo data - SAS](https://docs.fortytwo.io/identity-universe/iam-core/connectors/demodatasas/): There are two dedicated demo data connectors for a non-existing Norwegian municipality named Utkanten Kommune. This connector provides school information… - [Dottie](https://docs.fortytwo.io/identity-universe/iam-core/connectors/dottie/): Dottie. Identity and access management built on the data you already have about your people. - [Entra ID Inbound](https://docs.fortytwo.io/identity-universe/iam-core/connectors/entraidinbound/): In order for users to be able to use the Fortytwo Universe portal, we need to identify them. This is done by matching the oid claim in the Entra ID access… - [Entra ID SCIM](https://docs.fortytwo.io/identity-universe/iam-core/connectors/entraidscim/): In order for users to be able to talk to the Fortytwo Universe, we need to identify them. This is done by matching the oid claim in the Entra ID access… - [File upload](https://docs.fortytwo.io/identity-universe/iam-core/connectors/fileupload/): Certain first party based connectors is based on uploading files, because the source systems generate files on a schedule rather than having APIs. In… - [Helsepersonellregisteret](https://docs.fortytwo.io/identity-universe/iam-core/connectors/helsepersonellregisteret/): Connectoren mot Helsepersonellregisteret benytter Maskinporten-autentisering, slik at for å konfigurere tilgang må du følge Maskinporten-dokumentasjonen.… - [Maskinporten](https://docs.fortytwo.io/identity-universe/iam-core/connectors/maskinporten/): This is not a connector, but is used as authentication by several integrations. - [Simployer](https://docs.fortytwo.io/identity-universe/iam-core/connectors/simployer/): A first party connector that imports people, employments and organizational data from Simployer. - [SAP SuccessFactors](https://docs.fortytwo.io/identity-universe/iam-core/connectors/successfactors/): A first party connector that imports people, employments and foundation objects from SAP SuccessFactors over the OData API. - [Vigilo OnEdHub](https://docs.fortytwo.io/identity-universe/iam-core/connectors/vigiloonedhub/): A first party connector that imports schools, classes, pupils and teachers from Vigilo through the OnEdHub OneRoster API. - [Visma Enterprise Plus](https://docs.fortytwo.io/identity-universe/iam-core/connectors/vismaenterpriseplus/): Visma has a very old fashioned approach to APIs, where they need to install the API on a per customer basis, and the API is xml based. After getting the… - [Visma Flyktning og Voksenopplæring](https://docs.fortytwo.io/identity-universe/iam-core/connectors/vismaflyvo/): This connector is a file upload based connector, which requires setting up file upload. - [Synchronization](https://docs.fortytwo.io/identity-universe/iam-core/sync/): A connector import copies source data into connector objects. A full sync then reads those objects and applies the customer's sync rules to create,… - [Sync rules](https://docs.fortytwo.io/identity-universe/iam-core/sync/syncrules/): Sync rules are the bridge between a connector's connector space and the core objects in IAM Core. A connector brings data in, but on its own that data… - [Sync rule expressions](https://docs.fortytwo.io/identity-universe/iam-core/sync/syncrule-expressions/): Expressions are the small building blocks that compute values inside a sync rule. They appear in two places: in a rule's scope, where they must produce a… - [Common](https://docs.fortytwo.io/identity-universe/iam-core/objecttypes/common/): Every core object — CoreIdentity, CoreRelationship and CoreOrgUnit — shares the attributes on this page in addition to its own. - [CoreIdentity](https://docs.fortytwo.io/identity-universe/iam-core/objecttypes/coreidentity/): A CoreIdentity is a person: an employee, a student, a consultant, an agent. It holds what is true about the human being regardless of what they do — their… - [CoreOrgUnit](https://docs.fortytwo.io/identity-universe/iam-core/objecttypes/coreorgunit/): A CoreOrgUnit is a part of the organisation: a company, a department, a school, a class. Org units nest through their parent reference to form the… - [CoreRelationship](https://docs.fortytwo.io/identity-universe/iam-core/objecttypes/corerelationship/): A CoreRelationship is a CoreIdentity's relationship to a CoreOrgUnit. An employment is an example of a relationship. - [Primary relationship](https://docs.fortytwo.io/identity-universe/iam-core/primary-releationship/): The solution allows users to select their own primary relationship. This means that if you model employments as relationships, you can allow your end… - [API and PowerShell](https://docs.fortytwo.io/identity-universe/iam-core/api/): All API endpoints are authenticated with the customer's own Entra ID, through our multi tenant application Fortytwo Universe. This means that you can use… - [Authenticating PowerShell](https://docs.fortytwo.io/identity-universe/iam-core/api/authentication-powershell/): To use PowerShell to connect to the Fortytwo Universe proper authentication must performed. - [Connector API](https://docs.fortytwo.io/identity-universe/iam-core/api/connector-api/): The Connector API is how an API based connector populates its own connector space. It lets you bring data from any system into IAM Core, whether or not… - [Connector PowerShell Module](https://docs.fortytwo.io/identity-universe/iam-core/api/connector-powershell-module/): The module Fortytwo.IAM.Core.Connector is for building an API based connector in PowerShell. It wraps the Connector API and, more usefully, works out for… - [IAM Core Admin PowerShell Module](https://docs.fortytwo.io/identity-universe/iam-core/api/iamcoreadmin-module/): The module Fortytwo.IAM.Core.Admin exists for the purposes of managing the IAM Core solution through PowerShell. - [IAM Core Admin Powershell Examples](https://docs.fortytwo.io/identity-universe/iam-core/api/iamcoreadmin-examples/): The module Fortytwo.IAM.Core.Admin exists for managing the IAM Core data through PowerShell. - [Recommended hybrid configuration](https://docs.fortytwo.io/identity-universe/iam-core/recommended-hybrid-configuration/): Recommended hybrid configuration. Identity and access management built on the data you already have about your people. - [Collections](https://docs.fortytwo.io/identity-universe/collections/): Collections is a logical grouping of objects. Collection membership is evaluated using either one of two approaches, or a combination of both: - [Getting started](https://docs.fortytwo.io/identity-universe/collections/getting-started/): Admin consent must be granted to work with Identity Universe. This can be achieved by a Global Admin by following and accepting the Microsoft admin… - [Collection design patterns](https://docs.fortytwo.io/identity-universe/collections/plandesign/design-patterns/): Collections can be combined to model access based on organizational affiliation, identity attributes, manual approval, or a combination of these. - [Collection naming and metadata](https://docs.fortytwo.io/identity-universe/collections/plandesign/naming-and-metadata/): Consistent naming and metadata make collections easier to find, understand, automate, review, and maintain. - [Criteria collections](https://docs.fortytwo.io/identity-universe/collections/plandesign/criteria/): A criteria collection holds whoever matches its condition. This page documents how conditions are written. - [Joinable collections](https://docs.fortytwo.io/identity-universe/collections/plandesign/joinable/): A joinable collection is one people ask to be in, rather than one they match into. This page documents the join policy that controls who may ask and who… - [Group Link Overview](https://docs.fortytwo.io/identity-universe/collections/plandesign/group-link-overview/): Group Link connects an Identity Universe collection to a Microsoft Entra ID group. - [Group Link and Entra ID](https://docs.fortytwo.io/identity-universe/collections/plandesign/group-link-entraid/): Group Link connects an Identity Universe collection to a Microsoft Entra ID group, and keeps the group's membership aligned with the collection. - [Migration patterns](https://docs.fortytwo.io/identity-universe/collections/deployuse/migration-patterns/): This guide describes recommended patterns for migrating existing access models to Identity Universe collections. - [Group Link](https://docs.fortytwo.io/identity-universe/collections/deployuse/group-link-deploy/): Before connecting an existing Entra ID group, determine whether its current membership should be: - [Collections API](https://docs.fortytwo.io/identity-universe/collections/api/collections-api/): Refer to Authentication with PowerShell for details on how to obtain an access token. - [Collections PowerShell Module](https://docs.fortytwo.io/identity-universe/collections/api/collections-module/): The module Fortytwo.IAM.Collections is created for managing Identity Universe collections through PowerShell. - [Collections PowerShell examples](https://docs.fortytwo.io/identity-universe/collections/api/collections-examples/): The module Fortytwo.IAM.Collections is created for managing Identity Universe collections through PowerShell. - [GroupLink API](https://docs.fortytwo.io/identity-universe/collections/api/grouplink-api/): Refer to Authentication with PowerShell for details on how to obtain an access token. - [Collections troubleshooting](https://docs.fortytwo.io/identity-universe/collections/troubleshooting/troubleshoot-collections/): This guide provides a structured approach to troubleshooting Identity Universe collections across the web interface, API, PowerShell, membership… - [Group Link troubleshooting](https://docs.fortytwo.io/identity-universe/collections/troubleshooting/troubleshoot-grouplink/): Is the identity a member of the source collection? - [IAM Core attributes](https://docs.fortytwo.io/identity-universe/education/iam-core-attributes/): In order to use the education features, IAM Core must be populated with data from the school information system(s) you have through connectors. The… - [Internet policy](https://docs.fortytwo.io/identity-universe/education/internet-policy/): The internet policy feature enables teachers and other delegated personell to assign internet policies to students, either as one-time assignments ("From… - [Create policy definition](https://docs.fortytwo.io/identity-universe/education/internet-policy/create-policy-definition/): Creating a new policy definition requires you to complete the following steps, detailed in the sections below. - [Student password](https://docs.fortytwo.io/identity-universe/education/student-password/): The student password feature enables teachers and other delegated personell to set a new password for student accounts, both as a first time password and… - [Installation - Active Directory](https://docs.fortytwo.io/identity-universe/education/student-password/installation-ad/): If you have student accounts in Active Directory, this is the guide for you, as you will need to install the agent module and run it. - [Installation - Cloud only students](https://docs.fortytwo.io/identity-universe/education/student-password/installation-cloud-only/): If you have cloud only students, you need to consent to this application in order to grant read access. Next, in order to follow the principle of least… - [API and PowerShell](https://docs.fortytwo.io/identity-universe/education/api/): All education API endpoints are documented in the swagger. ## Managed Identity Services HR provisioning, criteria groups, Verified ID and other managed Entra services. - [Managed Identity Services](https://docs.fortytwo.io/managed-identity-services/): Welcome to Fortytwo Managed Identity Services. Here you will find documentation material related to our identity services. - [Bytt.Email](https://docs.fortytwo.io/managed-identity-services/Bytt.Email/): Bytt.Email is a service that allows end users to change their own email address and UPN, both in Entra ID and Active Directory, based on predefined patterns. - [Automatically configure everything](https://docs.fortytwo.io/managed-identity-services/Bytt.Email/autoconfig/): Automatically configure everything. The following PowerShell can be run as a global administrator. - [Step 1 - Consenting access](https://docs.fortytwo.io/managed-identity-services/Bytt.Email/config-step1/): As the first step of getting access to the Bytt.Email service, you need to consent two enterprise applications in your Entra ID. - [Step 2 - Configuring email/accountname patterns](https://docs.fortytwo.io/managed-identity-services/Bytt.Email/config-step2/): Patterns for Bytt.Email are configured through Entra ID groups with extension properties in your tenant. - [Step 3 - Grant users access](https://docs.fortytwo.io/managed-identity-services/Bytt.Email/config-step3/): Assigning access to the Bytt.Email service is done by locating the Fortytwo Universe app under Enterprise Apps. - [Step 4 - Configure write permissions / fulfillment](https://docs.fortytwo.io/managed-identity-services/Bytt.Email/config-step4/): In order to minimize the permissions required by Bytt.Email, we are not requesting permissions like user.readwrite.all, which would work, but would grant more access than we need. - [Step 5 - Install the Active Directory agent](https://docs.fortytwo.io/managed-identity-services/Bytt.Email/config-step5/): The ChangeEmail agent module is a simple module made for listening to change requests from Bytt.Email / ChangeEmail by Fortytwo, updating the user account in Active Directory and reporting back the status of the change. - [Step 6 - Licensing and final steps](https://docs.fortytwo.io/managed-identity-services/Bytt.Email/config-step6/): As a final step, you need to please subscribe to Bytt.Email through Azure Marketplace. - [Email address history](https://docs.fortytwo.io/managed-identity-services/Bytt.Email/email-address-history/): The service has a feature for keeping track of previously used email addresses, that ensures that an email address is not reused within a configurable number of days. - [Roles](https://docs.fortytwo.io/managed-identity-services/Bytt.Email/roles/): Bytt.Email has two different roles, both available for assignment through the Fortytwo Universe enterprise app. - [Testing patterns using the API](https://docs.fortytwo.io/managed-identity-services/Bytt.Email/testing-patterns-using-the-api/): In order to test your pattern groups using the Bytt.Email service, you need a user account that is assigned the Bytt.Email - administrator role, and an access token to access our API. - [Testing patterns using the PowerShell Module](https://docs.fortytwo.io/managed-identity-services/Bytt.Email/testing-patterns-using-the-powershell-module/): In order to test your pattern groups using the Bytt.Email service, you need a user account that is assigned the Bytt.Email - administrator role, and this PowerShell module. - [Using the API in your automations](https://docs.fortytwo.io/managed-identity-services/Bytt.Email/using-the-api-in-your-automations/): You can easily use the Bytt.Email API in your automations, such as for user provisioning of new employee accounts. - [Entra ID Advanced Criteria Groups](https://docs.fortytwo.io/managed-identity-services/entraid-advanced-criteria-groups/): Entra ID dynamic membership rules for groups are awesome, but let's face it, they are simply way too limited. That's why we built a simple open source solution that enables you to build as advanced scenarios as you'd like. - [Use module with an Automation Account](https://docs.fortytwo.io/managed-identity-services/entraid-advanced-criteria-groups/automation-account/): By using our dynamic group module with an Azure Automation Account, you can easily automate and schedule advanced group memberships. - [Examples](https://docs.fortytwo.io/managed-identity-services/entraid-advanced-criteria-groups/examples/): Examples of advanced criteria groups built with the AdvancedCriteriaBasedGroups PowerShell module. - [Fortytwo Managed Microsoft Entra External ID](https://docs.fortytwo.io/managed-identity-services/external-id/): Fortytwo's Managed External ID service provides a production-ready, enterprise-grade implementation of Microsoft Entra External ID for customer identity and access management (CIAM), delivered as a fully managed service. - [Dottie](https://docs.fortytwo.io/managed-identity-services/hr-provisioning/hr-systems/dottie/): In order for Fortytwo to connect to Dottie, we require a Client ID and Client secret configured under API access. - [Evolution HR](https://docs.fortytwo.io/managed-identity-services/hr-provisioning/hr-systems/evolution-hr/): In order for Fortytwo to connect to Evolution HR, we require a Client ID and Client secret configured under API access. - [Onboarding](https://docs.fortytwo.io/managed-identity-services/hr-provisioning/onboarding/): Thank you for your interest in our HR Provisioning service. In order to onboard to the service, the following steps are required. - [Fully restarting sync](https://docs.fortytwo.io/managed-identity-services/hr-provisioning/restarting-sync/): The Entra ID Inbound Provisioning API maintains a "sticky join", and the "Restart provisioning" button in the Entra ID portal does not clear this sticky join. - [Service description](https://docs.fortytwo.io/managed-identity-services/hr-provisioning/service-description/): Fortytwo HR Provisioning is designed to streamline and automate the synchronization of HR data with the identity platform through the Entra ID Inbound Provisioning API. - [How to use](https://docs.fortytwo.io/managed-identity-services/organizational-structure-groups/security-groups/how-to-use/): Through our "organizational structure as security groups"-service, we generate each element in the organizational hierarchy as security groups in Entra ID. - [Service description](https://docs.fortytwo.io/managed-identity-services/organizational-structure-groups/security-groups/service-description/): Organizational structure as security groups is designed to streamline and automate the synchronization of the HR organizational structure / hierarchy into an Entra ID security group structure. - [Microsoft Entra Verified ID Services by Fortytwo](https://docs.fortytwo.io/managed-identity-services/verified-id/): Fortytwo helps organizations design, implement, and optimize their verifiable credentials infrastructure with Microsoft Entra Verified ID. ## Marketplace Offerings Azure Marketplace products: AKS, landing zones, self-hosted runners and more. - [Marketplace Offerings](https://docs.fortytwo.io/marketplace-offerings/): A production-grade AKS cluster from Fortytwo on the Azure Marketplace that is secure by default. - [Github Runner Container Apps Job](https://docs.fortytwo.io/marketplace-offerings/github-runner-container-apps-job/): Self Hosted Github runners based on Jobs running in Azure Container Apps. - [Maester my Microsoft365](https://docs.fortytwo.io/marketplace-offerings/maester-my-microsoft365/): An easily deployable solution template on Microsoft Marketplace, that will make Maester run in your own environment, giving you control over the setup. - [Managed Azure Kubernetes Service](https://docs.fortytwo.io/marketplace-offerings/managed-azure-kubernetes-service/): A production-grade AKS cluster from Fortytwo on the Azure Marketplace that is secure by default. - [Installation](https://docs.fortytwo.io/marketplace-offerings/managed-azure-kubernetes-service/getting-started/1.%20Installation/): A quick walkthrough for installing the Managed Azure Kubernetes service application from the Azure Marketplace. - [Grant access to AKS](https://docs.fortytwo.io/marketplace-offerings/managed-azure-kubernetes-service/getting-started/2.%20Grant%20access%20to%20AKS/): How to grant yourself access to an Azure Kubernetes Service (AKS) cluster using Azure RBAC roles in the Azure portal. - [Connect to the cluster](https://docs.fortytwo.io/marketplace-offerings/managed-azure-kubernetes-service/getting-started/3.%20Connect%20to%20the%20cluster/): Connect to your Azure Kubernetes Service (AKS) cluster using Azure CLI commands. - [Secrets integration](https://docs.fortytwo.io/marketplace-offerings/managed-azure-kubernetes-service/getting-started/4.%20Secrets%20integration/): Set up the CSI Secret Driver for Azure, allowing Kubernetes to use secrets stored in Azure Key Vault using a user-assigned managed identity. - [ArgoCD UI](https://docs.fortytwo.io/marketplace-offerings/managed-azure-kubernetes-service/getting-started/5.%20ArgoCD%20UI/): Quickly expose the Argo CD server UI in your Kubernetes cluster and authenticate using the initial admin account. - [Using private github repositories](https://docs.fortytwo.io/marketplace-offerings/managed-azure-kubernetes-service/getting-started/6.%20Using%20private%20github%20repositories/): Set up access to a private GitHub repository in Argo CD for managing your applications. - [Deploy workloads](https://docs.fortytwo.io/marketplace-offerings/managed-azure-kubernetes-service/getting-started/7.%20Deploy%20workloads/): Deploy your workload using Argo CD by creating an application manifest that utilizes secrets from Azure Key Vault and targets your GitHub repository. - [Managed Grafana](https://docs.fortytwo.io/marketplace-offerings/managed-azure-kubernetes-service/monitoring/1.%20Managed%20Grafana/): Grafana is automatically deployed in your Managed Azure Kubernetes Service (AKS) environment to monitor, visualize, and analyze your Kubernetes workloads. - [Managed Prometheus](https://docs.fortytwo.io/marketplace-offerings/managed-azure-kubernetes-service/monitoring/3.%20Managed%20Prometheus/): Prometheus is an open-source monitoring and alerting toolkit that scrapes metrics from your Azure Kubernetes Service (AKS) cluster. - [Managed Azure Landing Zones](https://docs.fortytwo.io/marketplace-offerings/managed-azure-landing-zones/): A full Managed Azure Landing Zones implementation based on Microsoft Cloud Adoption Framework for Azure. - [Managed Desktop Light](https://docs.fortytwo.io/marketplace-offerings/managed-desktop-light/): A lightweight Managed Desktop solution for environments which require a simple, secure and low-cost desktop environment. - [Architecture](https://docs.fortytwo.io/marketplace-offerings/managed-desktop-light/Architecture/): The solution is based on a single Windows 11 multi-session host, joined to Azure AD. - [Backup](https://docs.fortytwo.io/marketplace-offerings/managed-desktop-light/Backup/): There is a weekly schedule for backup of the virtual machine, and the backup is stored in a Recovery Services Vault. - [Deployment](https://docs.fortytwo.io/marketplace-offerings/managed-desktop-light/Deployment/): Managed Desktop Light is deployed through the Azure Portal, using Azure Marketplace. - [End user Documentation for Managed Desktop Light](https://docs.fortytwo.io/marketplace-offerings/managed-desktop-light/End%20User/): How to connect to Managed Desktop Light from the Azure Virtual Desktop client. - [Privacy Policy](https://docs.fortytwo.io/marketplace-offerings/privacypolicy/): This Privacy Policy applies to the products and services we offer on the Microsoft AppSource and Azure Marketplace, as well as our related websites. - [Self Hosted Runners](https://docs.fortytwo.io/marketplace-offerings/self-hosted-runners/): Self hosted runners for Azure DevOps or GitHub, using an image that is continuously updated with the same cadence as the Microsoft Hosted Runners. - [Configuring Azure DevOps self hosted runners using VMSS](https://docs.fortytwo.io/marketplace-offerings/self-hosted-runners/ado/): Configure an Azure Virtual Machine Scale Set (VMSS) that will always be running the latest Self Hosted Runner image, and connect the VMSS as an agent pool in Azure DevOps. - [Step 1a - Configuring the Virtual Machine Scale Set manually](https://docs.fortytwo.io/marketplace-offerings/self-hosted-runners/ado/step1-manual/): Create the Virtual Machine Scale Set for the self hosted runners manually in the Azure Portal. - [Step 1b - Configuring the Virtual Machine Scale Set using Terraform](https://docs.fortytwo.io/marketplace-offerings/self-hosted-runners/ado/step1-terraform/): Deploy the Virtual Machine Scale Set for the self hosted runners using the published Terraform module. - [Step 2 - Configuring the Azure DevOps Agent Pool](https://docs.fortytwo.io/marketplace-offerings/self-hosted-runners/ado/step2/): Add the Virtual Machine Scale Set as an agent pool in Azure DevOps. - [Step 3 - Testing the self hosted runner](https://docs.fortytwo.io/marketplace-offerings/self-hosted-runners/ado/step3/): Test the self hosted runner with an example Azure DevOps pipeline using the pool you created. - [Configuring GitHub self hosted runners using VMSS](https://docs.fortytwo.io/marketplace-offerings/self-hosted-runners/github/): Configure an Azure Virtual Machine Scale Set (VMSS) that will always be running the latest Self Hosted Runner image, and automatically register the instances as self hosted runners in GitHub. - [Step 1a - Configuring the Virtual Machine Scale Set manually](https://docs.fortytwo.io/marketplace-offerings/self-hosted-runners/github/step1-manual/): Create the Virtual Machine Scale Set for the self hosted runners manually in the Azure Portal. - [Step 1b - Configuring the Virtual Machine Scale Set using Terraform](https://docs.fortytwo.io/marketplace-offerings/self-hosted-runners/github/step1-terraform/): Deploy the Virtual Machine Scale Set for the self hosted runners using the published Terraform module. - [Step 2 - Configuring the virtual machine scale set for auto registration](https://docs.fortytwo.io/marketplace-offerings/self-hosted-runners/github/step2/): Configure the virtual machine scale set to auto register the instances as GitHub self hosted runners. - [Step 3 - Testing the self hosted runner](https://docs.fortytwo.io/marketplace-offerings/self-hosted-runners/github/step3/): Test the self hosted runner with an example GitHub workflow. - [Privacy Policy for Self-Hosted Runners (Windows and Ubuntu)](https://docs.fortytwo.io/marketplace-offerings/self-hosted-runners/privacypolicy/): How Fortytwo collects, uses, and shares information when you use our Self-Hosted Runners Windows and Ubuntu Virtual Machine images. ## Azure AD B2C Customer identity with Azure AD B2C: app integration, policies and branding. - [Getting started](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/): Documentation for the Managed Azure AD B2C solution that is available in the Azure Marketplace. - [Microsoft B2C and the Identity Experience Framework](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/a-CIAM-IEF-introduction/): The Microsoft Identity Experience Framework (IEF) allows for full flexibility of the Microsoft Identity B2C platform. - [The Identity Experience Framework](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/d2-IEF/): The Identity Experience Framework supports custom policies, which are developed using Extensible Markup Language (XML). - [Authentication and Authorization](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/e1-AuthN-and-AuthZ/): The Microsoft Identity platform supports the authentication protocol standard OAuth 2.0 and the added identity layer OpenID Connect. - [Application integration](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/b-Application-integration/): How to integrate an application with the Identity platform, from app registrations and custom policies to authentication and integration examples. - [Creating or requesting an app registration](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/c1-Creating-an-app-registration/): To create an app registration some information about the app must be provided, depending on the type of application. - [OAuth 2.0 authorization code grant](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/e2-OAuth-AuthZ-code-grant/): The authorization code grant enables apps to securely acquire access_tokens, which can be used to access resources that are secured by an authorization server. - [OAuth 2.0 client credentials grant](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/e3-OAuth-Client-credentials-grant/): Use the OAuth 2.0 client credentials grant to access web-hosted resources by using the identity of an application. - [OAuth 2.0 implicit grant (see authorization code grant)](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/e4-OAuth-Implicit-grant/): Reference to understand how the implicit grant works, which should be replaced by the authorization code grant with PKCE. - [Validate OpenID Connect and OAuth 2.0 tokens](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/e5-Token-validation/): The best practice how to validate tokens issued by the Microsoft Identity platform. - [Nonce: Mitigate replay attacks when using implicit grant](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/e6-Nonce/): When using the implicit grant, a cryptographic nonce must be sent on authentication requests in order to mitigate replay attacks. - [Debugging OpenID Connect and OAuth 2.0](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/e8-Debug-OIDC-and-OAuth/): A couple of community tools that may prove useful for debugging OpenID Connect and OAuth 2.0. - [Security Assertion Markup Language 2.0 (SAML)](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/e9a-SAML/): SAML is a standard for exchanging authentication and authorization data between security domains. - [Azure AD B2C: Integrate SAML based applications](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/e9b-SAML-app-integration/): Using Security Assertion Markup Language 2.0 it is possible to integrate with SAML-based applications using custom policies. - [Custom branding - sign-in pages](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/d3-Custom-branding/): The sign-in pages are made of up html, css and javascript files, and can be maintained in an Azure storage account container. - [Identity Experience Framework custom policies](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/d4-Custom-policies/): Custom policies builds on top of the Identity Experience Framework (IEF) and enables the creation of User Journeys tailor-made for any organizational need. - [Automating upload of custom branding and policy files](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/d5-Pipeline-branding-policies/): The moving pieces that need to go together to build a pipeline for uploading custom branding and policy files across multiple environments. - [Pipeline deployment custom branding](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/d6-Pipeline-push-branding/): Management of custom branding files, the manual way with a PowerShell script or the automated way with Azure DevOps repositories and pipelines. - [Branding policies pipeline configuration](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/d9-Pipeline-branding-pipeline-config/): Azure DevOps pipelines are used for deploying the B2C user interface (branding) and policy files (User Journeys). - [DEV - tenant.onmicrosoft.com - app registrations](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/c2-DEV-App-registrations/): Template listing the app registrations that are used in application integrations in the DEV environment. - [DEV - tenant.onmicrosoft.com - user journeys](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/f1-DEV-User-Journeys/): Template listing the User Journeys (execution policies) available in the DEV environment. - [DEV - tenant.onmicrosoft.com - custom policy files](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/f2-DEV-Custom-policy-files/): Template listing the custom policy files that make up the User Journeys in the DEV environment. - [TEST - tenant.onmicrosoft.com - app registrations](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/c3-TEST-App-registrations/): Template listing the app registrations that are used in application integrations in the TEST environment. - [TEST - tenant.onmicrosoft.com - user journeys](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/g1-TEST-User-Journeys/): Template listing the User Journeys (execution policies) available in the TEST environment. - [TEST - tenant.onmicrosoft.com - custom policy files](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/g2-TEST-Custom-policy-files/): Template listing the custom policy files that make up the User Journeys in the TEST environment. - [PROD - tenant.onmicrosoft.com - app registrations](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/c4-PROD-App-registrations/): Template listing the app registrations that are used in application integrations in the PROD environment. - [PROD - tenant.onmicrosoft.com - user journeys](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/h1-PROD-User-Journeys/): Template listing the User Journeys (execution policies) available in the PROD environment. - [PROD - tenantname.onmicrosoft.com - custom policy files](https://docs.fortytwo.io/Managed%20Azure%20AD%20B2C/h2-PROD-Custom-policy-files/): Template listing the custom policy files that make up the User Journeys in the PROD environment. ## Entra Reference Architecture Reference designs for Microsoft Entra, including Norwegian municipalities. - [Microsoft Entra Solution Patterns](https://docs.fortytwo.io/Entra%20Reference%20Architecture/): This section contains our Fortytwo reference solutions for utilizing Microsoft Entra as your Identity Governance and Access (IGA) solution. - [Customer Identity and Access Management](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Customer%20Identity%20and%20Access%20Management/): Customer Identity and Access Management. Reference designs for Microsoft Entra, including Norwegian municipalities. - [Norske kommuner og fylkeskommuner](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/): Fortytwo's referansearkitektur for Identity and Access Management (IAM) / Identity Governance and Administration (IGA) for norske kommuner og fylkeskommuner, basert på Microsoft Entra ID. - [FEIDE + Microsoft Entra ID](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/FEIDE/): Alle kommuner og fylkeskommuner må tilby sine ansatte og elever en måte å logge på FEIDE på, og Fortytwo tilbyr FEIDE-katalog som en tjeneste. - [Gjestetilganger](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Gjester%20og%20eksterne/): Gjestetilganger. Reference designs for Microsoft Entra, including Norwegian municipalities. - [Integrasjon av tjenester](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Integrasjon%20av%20tjenester/): Designet legger opp til at alle applikasjoner og tjenester integreres mot Entra ID, både for Single Sign-On, autorisasjon og brukerprovisjonering der det er behov for det. - [App-roller og tildelinger](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Integrasjon%20av%20tjenester/Autorisasjon%20og%20grupper/01-App-roller%20og%20tildelinger/): App-roller og tildelinger. Reference designs for Microsoft Entra, including Norwegian municipalities. - [Etablere grupper i Claims](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Integrasjon%20av%20tjenester/Autorisasjon%20og%20grupper/02-Assigned%20groups%20as%20claim/): Etablere grupper i Claims. Reference designs for Microsoft Entra, including Norwegian municipalities. - [SCIM overføring av Grupper](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Integrasjon%20av%20tjenester/Autorisasjon%20og%20grupper/03-SCIM-transferred%20groups/): SCIM overføring av Grupper. Reference designs for Microsoft Entra, including Norwegian municipalities. - [Pipeline overføring av grupper](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Integrasjon%20av%20tjenester/Autorisasjon%20og%20grupper/04-Pipeline%20transferring%20app%20roles/): Pipeline overføring av grupper. Reference designs for Microsoft Entra, including Norwegian municipalities. - [Applikasjon initiert overføring av grupper](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Integrasjon%20av%20tjenester/Autorisasjon%20og%20grupper/05-Application%20reading%20groups/): Applikasjon initiert overføring av grupper. Reference designs for Microsoft Entra, including Norwegian municipalities. - [SCIM-basert Integrasjon](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Integrasjon%20av%20tjenester/Brukerprovisjonering/01-SCIM-basert%20integrasjon/): System for Cross-domain Identity Management (SCIM) er en standard protokoll innen identitetsadministrasjon, som lar organisasjoner enkelt håndtere identiteter og tilgang på tvers av ulike plattformer og applikasjoner. - [API-Basert Integrasjon](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Integrasjon%20av%20tjenester/Brukerprovisjonering/02-API-basert%20integrasjon/): Det finnes mange applikasjoner som har API-baserte grensesnitt for å populere brukere, men hvor APIet ikke er basert på SCIM-standarden. - [Fil-basert Integrasjon](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Integrasjon%20av%20tjenester/Brukerprovisjonering/03-Fil-basert%20integrasjon/): Fil-basert Integrasjon. Reference designs for Microsoft Entra, including Norwegian municipalities. - [Applikasjon initiert integrasjon](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Integrasjon%20av%20tjenester/Brukerprovisjonering/04-App-read%20integrasjon/): Applikasjon initiert integrasjon. Reference designs for Microsoft Entra, including Norwegian municipalities. - [On-Prem AD integrasjon](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Integrasjon%20av%20tjenester/Brukerprovisjonering/05-On-prem-AD-integrasjon/): On-Prem AD integrasjon. Reference designs for Microsoft Entra, including Norwegian municipalities. - [Våre ferdige integrasjon](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Integrasjon%20av%20tjenester/Ferdige%20integrasjoner/01-intro/): Våre ferdige integrasjon. Reference designs for Microsoft Entra, including Norwegian municipalities. - [Multi-tenant app for SaaS applikasjoner](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Integrasjon%20av%20tjenester/Single%20Sign-On/1/): Multi-tenant app for SaaS applikasjoner. Reference designs for Microsoft Entra, including Norwegian municipalities. - [OpenID Connect integrasjon](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Integrasjon%20av%20tjenester/Single%20Sign-On/2/): OpenID Connect integrasjon. Reference designs for Microsoft Entra, including Norwegian municipalities. - [SAML federering](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Integrasjon%20av%20tjenester/Single%20Sign-On/3/): SAML federering. Reference designs for Microsoft Entra, including Norwegian municipalities. - [Priviligert tilgang](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Priviligert%20tilgang/): Priviligert tilgang. Reference designs for Microsoft Entra, including Norwegian municipalities. - [Selvbetjeningsfunksjon for avansert gruppemedlemskap](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Selvbetjening/Avansert%20gruppeh%C3%A5ndtering/01-intro/): Selvbetjeningsfunksjon for avansert gruppemedlemskap. Reference designs for Microsoft Entra, including Norwegian municipalities. - [Selvbetjeningsfunksjon for delegert administrasjon/lederportal](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Selvbetjening/Delegert%20administrasjon/01-intro/): Selvbetjeningsfunksjon for delegert administrasjon/lederportal. Reference designs for Microsoft Entra, including Norwegian municipalities. - [Selvbetjeningsfunksjon for håndtering av elevpassord](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Selvbetjening/F%C3%B8rstegangspassord/01-intro/): Selvbetjeningsfunksjon for håndtering av elevpassord. Reference designs for Microsoft Entra, including Norwegian municipalities. - [Selvbetjeningsfunksjon for styring av internettilgang](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Selvbetjening/Internett%20styring/01-intro/): Selvbetjeningsfunksjon for styring av internettilgang. Reference designs for Microsoft Entra, including Norwegian municipalities. - [Sikkerhet og Conditional Access](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Sikkerhet%20og%20Conditional%20Access/01-intro/): Sikkerhet og Conditional Access. Reference designs for Microsoft Entra, including Norwegian municipalities. - [Autentiseringsmekanismer](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Sikkerhet%20og%20Conditional%20Access/02-Autentiseringsmekanismer/): Autentiseringsmekanismer. Reference designs for Microsoft Entra, including Norwegian municipalities. - [Nødtilgang](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Sikkerhet%20og%20Conditional%20Access/03-N%C3%B8dtilgang/): Nødtilgangskontoer (Også kalt Break Glass Account) i Entra ID gir et ekstra sikkerhetslag ved å tillate autoriserte personer å få tilgang til kritiske Entra ID-ressurser i tilfelle en uventet hendelse. - [Overvåkning](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Sikkerhet%20og%20Conditional%20Access/04-Overv%C3%A5kning/): Overvåkning. Reference designs for Microsoft Entra, including Norwegian municipalities. - [Persona Based Conditional Access](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Norske%20kommuner%20og%20fylkeskommuner/Sikkerhet%20og%20Conditional%20Access/05-Persona%20Based%20Conditional%20Access/): Persona Based Conditional Access. Reference designs for Microsoft Entra, including Norwegian municipalities. - [Outbound Provisioning](https://docs.fortytwo.io/Entra%20Reference%20Architecture/Outbound%20Provisioning/): Outbound Provisioning. Reference designs for Microsoft Entra, including Norwegian municipalities. ## Security How to report vulnerabilities and reach our security team. - [Report a Security Issue](https://docs.fortytwo.io/security/): If you believe you have found a security vulnerability in any of our services, products, or sites, we encourage you to let us know immediately. ## General Working with Fortytwo: shared channels, information labelling. - [Generic](https://docs.fortytwo.io/Generic/): This is currently a work in progress and more will come here... - [Document labelling](https://docs.fortytwo.io/Generic/Fortytwo%20information%20labelling/): Fortytwo Technologies principles in regards to information protection and document labelling. - [Shared Teams channel](https://docs.fortytwo.io/Generic/shared_teams_channel/): Set up and verify the needed configuration in your tenant to be able to join a shared Teams channel with Fortytwo.