Integrating the product and Azure Government Cloud Computing High Security(GCC)

Microsoft Azure Active Directory is now Microsoft Entra ID

Only Azure Government tenant administrators and experienced administrators should perform the steps in this article.3

Azure Government is the mission-critical cloud, delivering breakthrough innovation to US government customers and their partners. Only US federal, state, local, and tribal governments and their partners have access to this dedicated instance, with operations controlled by screened US citizens. The key difference between Microsoft Azure (Commercial) and Microsoft Azure Government is that Azure Government is a sovereign cloud. It's a physically separated instance of Azure, dedicated to U.S. government workloads only. It's built exclusively for government agencies and their solution providers.

Authorized administrators can configure K2 to integrate with an Azure Government tenant using this article. Only customers with access to an Azure Government tenant can have their environment configured to integrate with GCC and the product only supports GCC High Security.

For more information about AAD integration see Azure Active Directory in the ]User Guide. For information on manually integrating with Microsoft Azure (Commercial) see the topic Manually Configure K2 for Azure Active Directory (AAD). For information on inbound OAuth, see the KB article Configure AAD and K2 Services for Inbound OAuth.

High-level steps of the configuration

This list summarizes the high-level steps you need to follow to configure the product to integrate with Azure GCC. For a detailed guide, see the Detailed steps section below.

This procedure assumes that there has been no previous integration, and that this is a 'clean' install.

General configuration

  1. Install the Azure PowerShell module locally to manage Azure resources.

GCC configuration

  1. Add the following apps to your tenant:
    • K2 for Office 365
    • Exchange Online for K2
  2. Register SharePoint with your tenant.

Installation and configuration

  1. Install the product.
  2. Edit configuration files to integrate with Azure GCC.
  3. Configure the Exchange Feature in K2 Management.
  4. Install and configure Nintex K2 for SharePoint.
    1. Configure newly added OAuth Resources:
      • Microsoft Online (MSOA, AADMGMT)
      • SharePoint (add Nintex K2 for SharePoint app)

During the configuration you need the following information from your subscription. Copy and save these values down as you go.

Item Example Values
  • Microsoft Office 365 Application ID / Client ID
  • Exchange Online Application ID / Client ID
  • SharePoint Application ID / Client ID
304e7ece-9380-43ac-a35c-a4645d5bba5e
  • Microsoft Office 365 Client Secret
  • Exchange Online Client Secret
sO7Uu2gC84Gdx/Vb7jcaGqek7KrPAfGfcsjlMS5m6AE=

Detailed steps

Follow the steps here to install the product, configure, and integrate with Azure GCC. Some of the Azure management is handled through PowerShell commands. If you do not have the Azure PowerShell module installed, proceed with step 1.