nameidentifier claims is no longer in the token issued by Access Control Service(ACS) with newly created ACS

Hi,

In our existing ACS, when we add a new relying party with that associate with rule as bellow:

input claim type as

htp://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier

and output claim type as

htp://schemas.xmlsoap.org/ws/2005/05/identity/claims/name

When I used the ACS created previously, for token I received, I have

Received claims with existing ACS:

htp://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier:           testoem2,

htp://schemas.xmlsoap.org/ws/2005/05/identity/claims/name:             TESTOEM2-MS,

htp://schemas.microsoft.com/accesscontrolservice/2010/07/claims/identityprovider:                htps://wp8partnerservicesv1-tst.accesscontrol.windows.net/

but for the new ACS namespace, when I configure it exactly the same way, I receive

htp://schemas.xmlsoap.org/ws/2005/05/identity/claims/name:             TestOem2-MS,

htp://schemas.microsoft.com/accesscontrolservice/2010/07/claims/identityprovider:                htps://zackpartnerservice1-tst.accesscontrol.windows.net/'

The nameidentifier claim is no longer in the token.

Does anyone from Azure ACS team know what change in ACS might have cause this issue and how do I config the ACS so that I can get nameidentifier claim in the token too?

since my account is not verified, I use h_ttp instead of http in my question.

thank you,

Zach