[Bug]: App doesn't have an app_graph

[jerbob92]

Bug Description

It would make sense if the App also had access to app_graph, not just ActivityContext.

Steps to Reproduce

1. Use the app somewhere
2. Want to use the Graph API
3. No app_graph on the app

Expected Behavior

That app_graph is also available on the App class.

Actual Behavior

No app_graph on the App class.

SDK Version

2.0.0a20

Python Version

3.14.2

Additional Context

No response

[heyitsaamir]

This is an oversight. We need to able to do something like self.get_graph(tenantId: str). We'll need to use get_graph because, graph is an optional dependency, and also I believe you need to pass in the tenant id to get the appropriate graph token as well.

[jerbob92]

@heyitsaamir

Yeah, this is what I have in my wrapped App:

def get_app_graph(self, tenant_id: Optional[str] = None) -> "GraphServiceClient":
    return _get_graph_client(lambda: self._token_manager.get_graph_token(tenant_id))

tenant_id is optional and will be taken from the credentials if not set. So I think only really important for multi-tenant apps.

[heyitsaamir]

@heyitsaamir

Yeah, this is what I have in my wrapped App:

def get_app_graph(self, tenant_id: Optional[str] = None) -> "GraphServiceClient":
    return _get_graph_client(lambda: self._token_manager.get_graph_token(tenant_id))

tenant_id is optional and will be taken from the credentials if not set. So I think only really important for multi-tenant apps.

Yeah agree with this. I like this approach. @lilyydu any concerns? We should do the same thing in TS. The current TS approach of having app.graph imo is wrong, because it only works for single-tenant apps. We should move to this approach there as well.

[heyitsaamir]

microsoft/teams.ts#287 ah funny enough, we have a PR sitting that does exactly this.

[lilyydu]

No concerns, desired behaviour makes sense to me. When I was implementing samples w/ graph, it did feel a little clunky to me. Feel free to continue the work on it @heyitsaamir!