Hello @Sudheesh P.S ,
Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.
I understand that you are trying to enable weighted routing method in Azure Traffic Manager. You've added a Virtual Machine Scale Set endpoint with 90% weight, and it works fine but when you try to add an azure endpoint for AppService with 10% weight, it fails with an error and asks to try after some time.
There are some considerations which applies when configuring Web Apps as endpoints in Traffic Manager:
- Only Web Apps at the Standard SKU or higher are eligible for use with Traffic Manager. Attempts to add a Web App of a lower SKU fail. Downgrading the SKU of an existing Web App results in Traffic Manager no longer sending traffic to that Web App.
- When an endpoint receives an HTTP request, it uses the host header in the request to determine which Web App should service the request. The host header contains the DNS name used to start the request, for example contosoapp.azurewebsites.net. To use a different DNS name with your Web App, the DNS name must be registered as a custom domain name for the App. When adding a Web App endpoint as an Azure endpoint, the Traffic Manager profile DNS name is automatically registered for the App. This registration is automatically removed when the endpoint is deleted.
- Each Traffic Manager profile can have at most one Web App endpoint from each Azure region. To work around for this constraint, you can configure a Web App as an External endpoint. For more information, see the FAQ.
So, make sure the below conditions are met:
- You are using an Web App at Standard SKU or higher.
- You don't already have a Web App endpoint from the same region as the one you are trying to add in this Traffic Manager profile.
However, the failures related to the above issues should give an error as following: "Error: Some of the provided Azure Website endpoints are not valid".
The error "Error: There was an error processing your request. Try again in a few moments", that you are receiving looks like a portal issue. But I would still encourage you to check the above conditions are met before following the below instructions.
Since the error received by you seems like an Azure portal issue, I would request you to try adding the endpoint via Azure PowerShell or Azure CLI for now and check Azure Portal at a later time.
Try the Azure PowerShell New-AzTrafficManagerEndpoint
command following the below docs:
Or try to use Azure CLI az network traffic-manager endpoint create
command following the below docs:
Kindly let us know if the above helps or you need further assistance on this issue.
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.