Microsoft Azure Analysis Services (SSAS) - Import

Bridge Specifications

Vendor	Microsoft
Tool Name	Azure Analysis Services (SSAS)
Tool Version	9.0 (2005) to 15.x (2019)
Tool Web Site	https://azure.microsoft.com/en-us/services/analysis-services/
Supported Methodology	[Business Intelligence] Metadata Repository, Data Store (Physical Data Model, OLAP Dimensional Model, Stored Procedure Expression Parsing), BI Design (RDBMS Source, OLAP Source, Dimensional Target, Transformation Lineage, Expression Parsing) via .Net API
Data Profiling
Incremental Harvesting
Multi-Model Harvesting
Remote Repository Browsing for Model Selection

SPECIFICATIONS
Tool: Microsoft / Azure Analysis Services (SSAS) version 9.0 (2005) to 15.x (2019) via .Net API
See https://azure.microsoft.com/en-us/services/analysis-services/
Metadata: [Business Intelligence] Metadata Repository, Data Store (Physical Data Model, OLAP Dimensional Model, Stored Procedure Expression Parsing), BI Design (RDBMS Source, OLAP Source, Dimensional Target, Transformation Lineage, Expression Parsing)
Component: MicrosoftSqlServerRepositoryAsImport.MicrosoftAzureAnalysisServices version 11.2.0

OVERVIEW
This bridge imports Business Intelligence (BI) reporting metadata from Microsoft SQL Server Analysis Services (SSAS), including the analysis databases (OLAP Models) and Analysis Management Objects (AMO).
Bridge supports Analysis Services Tabular, Multidimensional and Azure Tabular models.

REQUIREMENTS
This bridge connects to the SQL Server Repository using the Analysis Services Management Objects (AMO). AMO client libraries are available as installable packages from NuGet.org and the bridge loads it automatically with Miscellaneous -d. You have to install these components with first running.

This bridge uses Windows Authentication to connect to Analysis Services by default. Please be sure the application is logged into Windows Domain as a User which has appropriate rights to the objects you wish to import when 'User' option is empty.

AUTHORIZATION
Use one of the following authentication methods based on the User and Secret parameter values:

- Microsoft SQL Server application credentials:
User = Application user
Secret = Application password

- Microsoft Azure Key Vault secret:
User = Application user (e.g. user@mail.com) added as "Analysis Services Server Admin" on target server.
Secret = Secret@VaultURL
For more information, see https://docs.microsoft.com/en-us/azure/key-vault/

- Microsoft Azure Secret credentials:
User = ClientID@TenantID
Secret = ClientSecret
For more information, see https://docs.microsoft.com/en-us/azure/key-vault/secrets/

- Microsoft Azure Temporary credentials (Externally MM managed cloud identity):
User = ""
Secret = ""
This is the first authorization method tried by default when both above parameters are empty.
For more information, see your Metadata Management (MM) / Data Catalog / Data Governance application documentation on managing cloud identity for metadata harvesting.

- Microsoft Azure Managed Service Identity (MSI):
User = ""
Secret = ""
This is the second authorization method tried by default when both above parameters are empty, however this authorization method can be forced with:
Miscellaneous = -auth.msi
For more information, see https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources

- Microsoft Windows Integrated Security:
User = ""
Secret = ""
This is the third authorization method tried by default when both above parameters are empty, however this authorization method can be forced with:
Miscellaneous = -auth.integrated

FREQUENTLY ASKED QUESTIONS
n/a

LIMITATIONS
Refer to the current general known limitations at MIMB Known Limitations or bundled in Documentation/ReadMe/MIMBKnownLimitations.html

SUPPORT
Provide a troubleshooting package with:
- the debug log (can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6)
- the metadata backup if available (can be set in the Miscellaneous parameter with option -backup)

In order to provide a complete set of source metadata to reproduce any SSAS issue, provide the exported Analysis Databases (XMLA) files.

Bridge Parameters

Bridge Mapping