should help you out Creating your proxies manually does not impede you from putting the configuration in the config file; you just need to expose the right constructor overload in your ClientBase-derived proxy class that delegates to the right constructor in ClientBase that takes the name of an endpoint to look up in the configuration. That said, you can of course fill in the endpoint identity through code, you just need to create the right kind of EndpointIdentity-derived class and attach it to the EndpointAddress object you use when you instantiate the proxy class. Something like this:
EndpointIdentity epid = EndpointIdentity.CreateUpnIdentity("email@example.com");
EndpointAddress epaddr = new EndpointAddress(uri, epid);
MyClient client = new MyClient(epaddr);
it fixes the issue OK, don't know why I couldn't find this before, but first thing Monday morning the answer pops up immediately: http://msdn.microsoft.com/en-us/library/aa347735.aspx The issuer element of the wsfederation is an endpoint config that allows you to set the user principal name within it.
I think the issue was by ths following , In your case, you want to batch the creation of multiple users. At present, the GraphClient does support batch processing but there are some limitation (Batch processing | Graph API concepts):
// Only 5 users per batch !!!!
var user1 = ...;
var user2 = ...;
var user3 = ...;
await activeDirectoryClient.Users.AddUserAsync(newStudentUser, deferredSave: true);
await activeDirectoryClient.Users.AddUserAsync(newTeacherUser, deferredSave: true);
await activeDirectoryClient.Users.AddUserAsync(newDirectorUser, deferredSave: true);
// In debug mode, you should use the SaveChangesAsync method with the default options
// Becasue the BatchWithIndependentOperations will not throw any exception even if there is a problem while creating the user.
adding users to ADGroupMember with userPrincipalName
I think the issue was by ths following , The problem here is that the -Members parameter of Add-ADGroupMember requires an identifier that is not UserPrincipalName. So you need to query for another identifier based on UserPrincipalName in this case. Since -Members accepts an array of ADPrincipals, you can update the membership with one command.