Open CeciAc opened 4 years ago
@CeciAc Thank you for the feedback! We are investigating this and will get back to you shortly.
@SunnyDeng I think that "pay-as-you-go" may be a mistranslation of "consumption." The intended meaning of the "consumption" plan is that you only pay for "resources consumed during function execution." I don't think "pay as you go" is correct in this context. #assign:SunnyDeng
@go-shinyashiki there is no easy way to add a function app to an existing Consumption plan like you can an app service plan or Premium plan. There is also no benefit to doing this as because each Consumption plan function app is scaled and managed independently even if in the same plan.
@ggailey777 Thanks for your reply. My request was to remove that wording from the documentation. I have now checked the documentation and confirmed the phrase has been removed, so you can close the case. Thank you very much.
Comments below were machine-translated
@go-shinyashiki commented on Thu Jun 11 2020
Azure Functions scale and hosting> Pay as you go plans
For the above 1 sentence on the page, I tried the following operation on the GUI. -When creating a new Azure Function, specify the App Service Plan that is configured with the hosting plan "Pay-as-you-go" already created in the Azure portal.
As a result, the App Service Plan configured with Pay-As-You-Go was not displayed when selecting the plan and the new Azure Function could not be assigned to an existing pay-as-you-go plan. If the documentation is incorrect, I would appreciate it if you could delete the one sentence in question.
ドキュメントの詳細
⚠ このセクションを編集しないでください。 docs.microsoft.com で必須です ➟ GitHub の問題のリンク。
@srvbpigh commented on Thu Jun 11 2020
Hello, @go-shinyashiki
Thank you for your feedback.
We are actively reviewing your comments and will get back to you soon.
Kind regards, Microsoft DOCS International Team