Microsoft
MicrosoftPlease see the note in the docs about the bug. Link provided below. We are working to address this as soon as possible. We've provided mitigations in the doc in the meantime. We appreciate the patience while we work through this.
Hi jordanselig
I've had a read through the learn.microsoft link but the workarounds don't seem to b e relevant for the issues we're facing:
Before this change, we were able to deploy multi ASPs onto the same /28 subnet without issue. However, since the change, we're receiving an error if an ASP already exists. We are not using multi-plan subnet join in anyway at all.
Is there any workaround for this scenario at present? If not, do you have ETA for the fix yet? It's starting to have a bit of an impact on our deliverables.
Thanks!
MicrosoftHi DarlyGarves. Not sure I understand the issue you're facing. can you please clarify the below statement?
we were able to deploy multi ASPs onto the same /28 subnet
this implies that you're using MPSJ since it's the same subnet. please let me know if I'm misunderstanding.
Hi, sorry for the confusion!
Before MPSJ went GA, we were able to deploy multiple App Service Plans into the same /28 subnet without doing anything special.
Since the release of MPSJ, we have discovered we can now only deploy one App Service Plan to a /28 subnet. If we try to add a second, we get this error:
Minimum subnet size allowed for joining multiple App Service Plans to same subnet is /26, the subnet attempting to be joined is /28
If I'm completely honest, I don't actually understand what MPSJ does because I was already able to deploy multiple App Service Plans into the same subnet before it was released! In my situation, the only change we've seen is it stops us from doing what we were able to do previously in /28 subnets?
I've never pro-actively configured MPSJ or anything and I'm not keen on having to re-IP our existing environments into new ranges so we can continue to create more.
Hope this makes more sense.
MicrosoftGot it. So it sounds like you were using MPSJ while it was in preview. Before preview, you were not able to join multiple plans to the same subnet. So you were unknowingly using it and reaping the benefits 😀
While in preview, we were not enforcing the /26 subnet requirement. There was a note in this blog post calling out that we would be enforcing that at GA, which is why you only recently started having this issue. This post was updated when we went GA and now states that /26 minimum is required.
The only way around this is most likely to go back to the old way of doing things which was by doing one vnet integration per App Service plan. If you want to continue having multiple plans with the same subnet for new integrations, you must meet the /26 requirement.
