Read only replica part of always on availability group for Reporting
My questions is will there be any problem if the read only replica for reporting is included as part of the always on availability group instead of setting Transaction Replication with the Listener.


Nothing you're not already dealing with such as an extra copy of the database, more networking IO, disk IO, etc., so that's kind of a moot point assuming the reporting server isn't massively underpowered for the reports you're running.

To be quite up front about it, I don't believe using transactional replication with Availability Groups is a good idea - it's technically possible, but beyond a pain to administrate over the long term unless you expect to never have a failover or swap in and out servers in the AG. The only time I'd go this route is if you only needed an extremely mall subset of data with vastly different indexes for reporting and couldn't do this on your primary. Outside of that I'd try my best to stay away from AGs + TR.