Additional SQL Server features and topics not covered by specific categories
The documentation says about AVAILABILITY_REPLICA:
An Always On Availability Groups secondary replica is applying transaction log records of this database to a corresponding secondary database.
I don't really see why the full backup would not permit log records from being applied. Then again, if I have it right, the log on the secondary cannot be truncated while the backup is running, so may be this is the problem. In any case, I would let that initial backup complete before I sound any alarm.
If the log space is released when the full backup has completed, you could try to shrink the log. However, this is will not be the last full backup taken on the MI, so it may be that because you have a new situation, you will need a bigger transaction log than before.