A good understanding of SQL databases and how to join tables in a SQL query is required for Enterprise Insights. You must also have knowledge on how to build reports and dashboards in a data visualization tool like Tableau or Power BI and how to connect it to a SQL data source.
The data schema document on the Jira Align Knowledge Base has information on the tables, columns, data types, and primary/foreign key mappings. You will need to create a login for the Jira Align Knowledge Base to access the schema document. All data in Jira Align is eligible to be exported to Enterprise Insights.
You will need your corporate network IP address range to be whitelisted on your Enterprise Insights instance by Atlassian. Please get in touch with your Technical Account Manager (TAM) or Enterprise Advocate (EA) for assistance.
There are two authentication options available: Azure Active Directory (AD) authentication and SQL login (username and password provided by Atlassian).
Azure AD authentication is recommended due to it being more secure. If you are using Azure AD, your Azure AD tenant must be enabled for guest authentication tenant access to allow authentication with Enterprise Insights. You can learn more on Microsoft’s website here.
No, Enterprise Insights does not support SSO or 2FA. However, Enterprise Insights does support Azure Active Directory (AD) authentication, which supports SSO and 2FA. You can learn more about Azure Active Directory single sign-on here.
Data is encrypted at rest by default using Azure’s transparent data encryption (TDE). Azure’s TDE uses the AES-256 encryption algorithm. Documentation on Azure’s TDE encryption is available on Microsoft’s documentation site.
Yes, although Azure does not have the same concept of VPCs. We are able to isolate your Enterprise Insights instance by deploying it into a private resource group where all of their components are unique to that resource. The only thing that is shared is Active Directory which is at the tenant level.