Error when trying to set Organizationalaccountsuffix through Set-AdfsClaimsProviderTrust

Question

I'm in the process of migrating from ADFS 2.0 to 3.0 for our Office 365 integration. It has mostly gone over quite painless being able to export and import the rules quite easily. However on the old system clients where able to log in with just their username
and adfs would take care of the suffix.
ADFS3.0 doesn't appear to do this for me at the moment and then I read that you can set the Organizational Account Suffix through Set-AdfsClaimsProviderTrust
However when I try to run
Set-AdfsClaimsProviderTrust -TargetName <targetname> -OrganizationalAccountSuffix @("<suffix>")
 I get the following error and I don't really understand what it means or what i can do to resolve it. 
Set-AdfsClaimsProviderTrust : PS0027: No properties except AcceptanceTransformRules, 
AcceptanceTransformRulesFile and ClaimOffered can be modified on the ADAuthority claims provider trust.
At line:1 char:1
+ Set-AdfsClaimsProviderTrust -TargetName "Active Directory" -OrganizationalAccoun ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (Microsoft.Ident...msProviderTrust:ClaimsProviderTrust) [Set- 
AdfsClaimsProviderTrust], ArgumentException
+ FullyQualifiedErrorId : PS0027,Microsoft.IdentityServer.Management.Commands.SetClaimsProviderTrustCommand
Any ideas?
Regards, 
Jacob

Answer 1

Hi Jacob,
That's something else:  an alternate login identifier. That's a suffix-based mechanism for logon using an alternate attribute to that of sAMAccountName or UPN. You asked "how to logon using your username and AD FS will take care of the suffix"...
that's not what this solution will do.  Whereas in AD FS 2.0 it's possible to logion without a domain prefix using just your sAMAccountName.. in AD FS 3.0, this is not possible without customization of Javascript as described here ..
Regards,
Mylo
http://blog.auth360.net