Skip to content

Commit d36f120

Browse files
authored
Merge pull request #99089 from rahulten/patch-1
Added consideration and limitation section
2 parents 8bc5d77 + 1a2bfc2 commit d36f120

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/analysis-services/analysis-services-manage-users.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,9 +71,13 @@ Roles at this level apply to users or accounts that need to perform tasks that c
7171

7272
By default, when you create a new tabular model project, the model project does not have any roles. Roles can be defined by using the Role Manager dialog box in Visual Studio. When roles are defined during model project design, they are applied only to the model workspace database. When the model is deployed, the same roles are applied to the deployed model. After a model has been deployed, server and database administrators can manage roles and members by using SSMS. To learn more, see [Manage database roles and users](analysis-services-database-users.md).
7373

74+
## Considerations and limitations
75+
76+
* Azure Analysis Services does not support the use of One-Time Password for B2B users
77+
7478
## Next steps
7579

7680
[Manage access to resources with Azure Active Directory groups](../active-directory/fundamentals/active-directory-manage-groups.md)
7781
[Manage database roles and users](analysis-services-database-users.md)
7882
[Manage server administrators](analysis-services-server-admins.md)
79-
[Azure role-based access control (Azure RBAC)](../role-based-access-control/overview.md)
83+
[Azure role-based access control (Azure RBAC)](../role-based-access-control/overview.md)

0 commit comments

Comments
 (0)