Utilizing two data services with shared ids from an application bad design?

Is utilizing two separate data services which don't know about each other but use the same id's so that my application can combine their data bad design? and if so how might I make it good design?

I'm working on an application which has two data services that it utilizes, one is a system that is managed by a third party and one is owned by myself.

The two data systems store mostly different types of data however there is some cross over between items such as Userids and TeamIds with my application getting an id from the third party service and pushing it up to the data service I own.

My question is about whether this is "good design" or if I am using some architecture anti-pattern? I'm finding when I want to display data that is a combination of the two services I am having to make multiple calls to my service then the third party service and provide some business logic to combine the two which feels like too much work.