Hi,
I have downloaded the dynamics 365 on premises VHD from LCS on clients premises, I already signed in with my account (partner account with Federation services with Microsoft) how ever clients users on their domain want to log in as well, I added them as a users on Dynamics with their emails, and invited them through LCS on the project as an operation users, they are still unable to log in , have I missed any step ?
Thank you in advance.
*This post is locked for comments
Avinesh it is better to create a new question to keep the forums clean.
How were you able to get the VHD? I am struggling with setup.
Thank you All, I had to provision the office 365 after creating it on the vhd, and it worked perfectly.
Thanks.
Thank you Vilmos,
I tried to create a new account on office 365 and while logging in to ERP I received the message you are not authorized , however I already added the new account in the AX 7 users.
Thank you,
You could try to reset the password for the account in the Active Directory console.
Two possible options for passwords are : Pass1Word and pass@word1 , You can also try and use admin user provisioning tool.
thanks a lot Maciej,
I tried you solution however when logging in with Username: suzan@contosoax7.onmicrosoft.com ,but am receiving the message "old password is used please enter the new password" then whatever password I fill I receive message incorrect username or password,
Thank you,
Hi, i think other users have misunderstood Your question, i think You are asking about contoso VHD. Not real on-premises deployment which doesn't have VHD type machines.
To add users to contoso D365 environment You have to enable personas in it. Here's how to do it :
When Microsoft created the Contoso demonstration company, they also did investigation which personas would be working in the fictional company. So users and example roles are provided as outcome. When you look at the current demonstration database there are some users like:
When you login as one of the Contoso employees the number of functionality is limited, meeting the permissions of this user and demonstration is more smoothly. The audience will not be overwhelmed by all possible functionality, but can focus on the process being demonstrated.
However when you run Microsoft Dynamics AX on your own tenant, login with a Contoso user is not working. Even when the user is enabled. You have to change settings on the users to be able to activate them running in your environment.
Microsoft Dynamics AX is using Azure Active Directory for user authentication. Where you could setup a federation and have claims based users in Microsoft Dynamics AX 2012, you can now setup any user in your Microsoft Dynamics AX environment. There is only one rule. If the users does not belong to your Azure tenant, you have to specify the domain from the third party within the Domain field of the AX user.
By default the value in this field is https://sts.windows.net/. To have a third party user activated you need to add the domain behind this value. In this example this is contosoax7.onmicrosoft.com. So the full domain should be filled with the next value: sts.windows.net/contosoax7.onmicrosoft.com. When you save the user record, AX will also retrieve the Identity provider and a correct SID value. This will also work with any other third party domain when the users are setup as user in an Azure Active Directory.
Now you are able to start Microsoft Dynamics AX using the credentials from e.g. Susan. Open a browser and use the next credentials:
Username: susan@contosoax7.onmicrosoft.com
Password: Pass1Word
Note that some Contoso users might have other passwords. The most are setup using the password as mentioned above. The workspace and available menus will now look like the screenshot below for the sales clerk. You can notice that the default dashboard already contains less options. The same is valid for the main menu compared with system administrator rights.
Also quick script that will enable them all :
class ActivateContosoPersonas { /// <summary> /// Runs the class with the specified arguments. /// </summary> /// <param name = "_args">The specified arguments.</param> public static void main(Args _args) { AxaptaUserManager manager = new AxaptaUserManager(); UserInfo userInfo; xAxaptaUserDetails userDetails; var contosoTenant = "contosoax7.onmicrosoft.com";
ttsbegin; userInfo.skipAosValidation(true);
while select forupdate userInfo { if (strContains(userInfo.NetworkAlias, contosoTenant) && !strContains(userInfo.networkDomain, contosoTenant)) { userInfo.networkDomain += contosoTenant; UserInfo.IdentityProvider = Microsoft.Dynamics.AX.Security.AuthenticationCommon.AadHelper::GetCanonicalIdentityProvider(UserInfo.networkDomain); userDetails = manager.getSIDFromName(UserInfo.networkAlias, UserInfo.IdentityProvider, UserInfo.accountType); userInfo.sid = userDetails.getUserSid(0); userInfo.update(); } }
ttscommit; }
}
Hello MDeeb,
In the Hosts file of every client machine you have to "point" to the server where the test instance is. You can find the file in: C:\Windows\System32\drivers\etc. There you edit the file and provide the IP address of the server and your URL for testing.
I hope this helps.
Please see if this blog may help
Mohamed Amine Mahmoudi
100
Super User 2025 Season 1
Community Member
48
Zain Mehmood
6
Moderator