Azure/login github action always looks for 'environment' entity type despite specifying other entity types in app registration

Hello, I’m trying to use ‘OIDC federated credentials’ using app registration -> federation credentials. Azue/login github actions always looks for entity type ‘environment’ despite specifying other entity type such as ‘pull_request’.

If I specify ‘environment’ in entity_type in app registration, the github actions works:

Run azure/login@v1
  with:
    client-id: <client-id>
    subscription-id: <sub-id>
    tenant-id: <tenant-id>
    enable-AzPSSession: false
    environment: azurecloud
    allow-no-subscriptions: false
    audience: api://AzureADTokenExchange
Using OIDC authentication...
Federated token details: 
 issuer - https://token.actions.githubusercontent.com 
 subject claim - repo:<org/repo>:environment:terraform-demo

If I specify any other type of ‘entity type’, the github action still looks for enviornment entity type as below:

Run azure/login@v1
Using OIDC authentication...
Federated token details: 
 issuer - https://token.actions.githubusercontent.com 
 subject claim - repo:<org/repo>:environment:terraform-demo
/usr/bin/az cloud set -n azurecloud
Done setting cloud: "azurecloud"
Error: : AADSTS70021: No matching federated identity record found for presented assertion. Assertion Issuer: 'https://token.actions.githubusercontent.com'. Assertion Subject: 'repo:<org/repo>:environment:terraform-demo'. Assertion Audience: 'api://AzureADTokenExchange'.
Trace ID: 3940b0d0-43bf-4048-a7bb-8fea435ab300
Correlation ID: 58e6c5ab-e623-4b92-9a53-a9b0ce85ee6d
Timestamp: 2022-01-15 10:55:55Z

[N-Usha]

Just for reference , here is the doc that clarifies the point @kchandra548 mentioned above : https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#filtering-for-pull_request-events

[BALAGA-GAYATRI]

@pavanm-huma assuming the above comments and referred docs helped you with azure login action and closing this issue. Feel free to reopen this issue if are still facing the problem. We will be happy to help you.