Thanks! Greg Taylor - EXCHANGE
I read through already may be i missed this part. So we can assume
EWSAllowedAppIDs gives administrators a practical way to identify remaining dependencies, limit EWS access to approved applications, and reduce the risk of disruption as retirement enforcement begins.
This feature is starting to roll out now. All tenants should be able to view the parameter when running Get-OrganizationConfig, but they won’t be able to set the list until the roll out reaches the tenant.
I didn't set through using below command
Set-OrganizationConfig -EwsAllowedAppIDs "d3590ed6-52b3-4102-aeff-aad2292ab01c, b52893c8-bc2e-47fc-918b-77022b299bbc, a672d62c-fc7b-4e81-a576-e60dc46e951d, f8d98a96-0999-43f5-8af3-69971c7bb423" this command
Instead below command is what we used.
# Read the current allow list
$current = (Get-OrganizationConfig -RetrieveEwsOperationAccessPolicy | Select-Object -ExpandProperty EwsAllowedAppIDs)
# Define the new App ID to add
$newAppId = "d3590ed6-52b3-4102-aeff-aad2292ab01c, b52893c8-bc2e-47fc-918b-77022b299bbc, a672d62c-fc7b-4e81-a576-e60dc46e951d, f8d98a96-0999-43f5-8af3-69971c7bb423"
# Combine existing and new values
$updated = @($current, $newAppId)
# Write the updated allow list back
Set-OrganizationConfig -EwsAllowedAppIDs ($updated -join ",")
Get-OrganizationConfig -RetrieveEwsOperationAccessPolicy | Select-Object -ExpandProperty EwsAllowedAppIDs
d3590ed6-52b3-4102-aeff-aad2292ab01c, b52893c8-bc2e-47fc-918b-77022b299bbc, a672d62c-fc7b-4e81-a576-e60dc46e951d, f8d98a96-0999-43f5-8af3-69971c7bb423
Let me know if this is not correct?