Robér Hinz

Great workaround @daanlenaerts ! To prevent the duplication of authorization policies, you can use the `IAuthorizationPolicyProvider`: ```csharp public class HttpRequestInterceptor : DefaultHttpRequestInterceptor { private readonly IPolicyEvaluator _policyEvaluator; private readonly IAuthorizationPolicyProvider...

I can verify this issue. Tested with Azure.Messaging.ServiceBus 7.12.0 Workaround with new parent activity: ```csharp private async Task HandleMessage(ProcessMessageEventArgs arg) { var parentId = arg.Message.ApplicationProperties["Diagnostic-Id"].ToString(); using var activity = _activitySource.StartActivity(nameof(HandleMessage),...

Any updates for the authorization issue of reference resolvers? When can we expect a fix for it?

Is there any workaround so far to rename the ``PageInfo`` type to avoid the conflicts in a federation scenario?

Here is a very easy way to add the ``@shareable`` directive to the ``PageInfo`` type without any hacks: ```csharp public class PageInfoType : ObjectTypeExtension { protected override void Configure(IObjectTypeDescriptor descriptor)...