search

microsoft / startstopv2-deployments

MIT License
53 stars 30 forks source link

Doesn't work in private networks #85

Open cpen-blm opened 1 year ago

cpen-blm commented 1 year ago

There is a need to have pre-configured storage when the requirement is to use private networking. Please update to include the option to have storage pre-deployed prior to this app and to be able to select that storage. This errors our with: { "status": "Failed", "error": { "code": "BadRequest", "message": "Creation of storage file share failed with: 'The remote server returned an error: (403) Forbidden.'. Please check if the storage account is accessible.", "details": [ { "message": "Creation of storage file share failed with: 'The remote server returned an error: (403) Forbidden.'. Please check if the storage account is accessible." }, { "code": "BadRequest" }, {} ] } }

RobSwoss commented 1 year ago

We have the same problem. We also tried to create the storage account beforehand. Unfortunately this didn't work.

oramoss commented 1 year ago

Yes, can't use this when we want our resources vnet injected.

cpen-blm commented 1 year ago

Then this is unusable in orgs that require privtae networking and perhaps zero trust which is unfortunate. If you cannot fix that could you please place that info in the readme as pre-reqs? Thanks!