Hello @AudunSolemdal ,
I've updated the following doc with the private endpoint traffic information in a NOTE as below : https://docs.microsoft.com/en-us/azure/virtual-wan/manage-secure-access-resources-spoke-p2s
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.
Hello @EnterpriseArchitect ,
You can check it by going to the devices page in your Azure Active directory (Azure AD --> Devices --> All Devices) or click on this direct link. You will see all the devices listed with the join type information as below:
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.
Hello @robcool ,
Thank you for the update. Glad to hear that the issue is resolved.
Could you please confirm if you renamed this profile name "SelfAsserted-ProfileUpdate"? What did you rename it to?
Regards,
Gita
Hello @IsabelFernandes-7967 ,
Yes, this has now changed.
As outlined in this article, only the Enterprise Agreement subscriptions do not have a port 25 block. On all other subscription types, the Azure platform will block outbound SMTP connections on TCP port 25. If you're using a non-enterprise subscription type, we encourage you to use an authenticated SMTP relay service.
https://docs.microsoft.com/en-us/azure/virtual-network/troubleshoot-outbound-smtp-connectivity
If you are already using an Enterprise Agreement subscription and need help with port 25 unblock, you need to contact support to get it unblocked.
Regards,
Gita
Thank you for the update, @50184869. Glad to hear that issue was resolved.
Please let us know if you encounter this issue again and share the co-relation ID, so that we can check the reason for failure.
Regards,
Gita
Hello @VincentGo-2585 ,
To allow Ingress Traffic from Azure Bastion control plane: you need to enable port 443 inbound from GatewayManager service tag. It is available in the source service tag as below:
As you don't see any other service tags in the source of your NSG apart from the 3 listed, could you please check if there is any policy restricting the listing of all service tags in your NSG within your subscription?
Regards,
Gita
Hello @DeshmukhVijit-2829 ,
Do you have a corporate proxy which is blocking this connection?
The only references that I found for this issue are as below:
https://github.com/MicrosoftDocs/azure-docs-cli/issues/2455
https://stackoverflow.com/questions/55463706/ssl-handshake-error-with-some-azure-cli-commands
Could you try to sign in using an Azure DevOps personal access token (PAT)?
Refer : https://docs.microsoft.com/en-us/azure/devops/cli/log-in-via-pat?view=azure-devops&tabs=windows
If it doesn't work, try posting the issue in the dedicated Developer Community.
Refer : https://developercommunity.visualstudio.com/spaces/21/index.html
Or, if you have a support plan, I request you file a support ticket, else please do let us know, we will try and help you get a one-time free technical support.
Regards,
Gita
Hello @atanugupta ,
Could you please provide an update on this post?
Kindly let us know if the above helps or you need further assistance on this issue.
Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.