Forum Discussion
Connector
I recently setup the SSAS Connector for a non-O365 client. Everything that Anonymous provided as reference is relevant. Even without O365, you will still have an Azure AD domain (<something>.onmicrosoft.com). In order to login to Power BI with your @companyname.com account, will need to go through the Azure AD steps at portal.office.com or in Azure Management to verify your company's domain. This has to be done regardless of whether you want to manage users independently as "cloud" users or whether you either want password sync or single sign-on by syncing with Azure AD Connect.
Once the domain has been added and verified, you can setup the SSAS Connector. The only change that you would need to make in local AD would be to change each user's domain from <companyname>.local to @companyname.com. This does not change their sign-on in the format domain\user, so they are still able to access everything in the domain as before. It does allow the local and Power BI login domains to match so that you do not receive the Effective User Name mismatch error.
I recently setup the SSAS Connector for a non-O365 client. Everything that Anonymous provided as reference is relevant. Even without O365, you will still have an Azure AD domain (<something>.onmicrosoft.com). In order to login to Power BI with your @companyname.com account, will need to go through the Azure AD steps at portal.office.com or in Azure Management to verify your company's domain. This has to be done regardless of whether you want to manage users independently as "cloud" users or whether you either want password sync or single sign-on by syncing with Azure AD Connect.
Once the domain has been added and verified, you can setup the SSAS Connector. The only change that you would need to make in local AD would be to change each user's domain from <companyname>.local to @companyname.com. This does not change their sign-on in the format domain\user, so they are still able to access everything in the domain as before. It does allow the local and Power BI login domains to match so that you do not receive the Effective User Name mismatch error.
deldersveld thanks, that is what I was looking for. Your detailed explanation exactly fits my scenario.
Anonymous sorry if I did not explain my question that well. Appreciate the references you included in your response.