Azure API method didn't download LX packages - manually finish?

While waiting for the client to renew expired support :\ I thought I'd post here to see if anyone else ran into this problem and might have a solution.

We deployed the Azure Active/Standby arm template with API failover method. However, the F5s need broad internet access to download the necessary LX packages required for the API failover. Ours of course did not have that and instead of opening fw ports and redeploying, they want to see if we can proceed with somehow manually resolving this.

My F5 rep suggested that this may be just an "install" script that goes out and downloads these and that restarting it may finalize the LX downloads. I just wanted to see if anyone else has run into this issue and what the resolution might be?

When I deployed in my azure lab, the api failover worked out of the box without any additional configuration.

Thanks!!