Hi,
I have a question about the administration aspect of Azure's Traffic Manager, as it's creating a very inconsistent experience to maintain. It seems that if you create a Traffic Manager Profile in the new portal (portal.azure.com), those resources are neither visible in the old portal (manage.windowsazure.com) nor in Powershell via the Get-AzureTrafficManagerProfile commandlet. However, Traffic Manager resources created in the old portal are visible everywhere (old, new and PowerShell). Here's an example screenshot. I have the two portals side by side, on the same subscription, and also the output of Get-AzureTrafficManagerProfile. Note that the New portal shows more Traffic Manager Profiles (question marks are beside them) that are missing from both the old portal and PowerShell which are missing instances, but are consistent: http://i.imgur.com/Bubxvcl.png
Is this by design? If not, will this be addressed? I am concerned because the old portal has two warning messages saying"Traffic Manager will be available only in the new portal after 2/1/2017. Try Traffic Manager in the new portal now?" and"Some of your resources might be visible only in the new Azure portal." which is completely accurate, but how am I supposed to update them via PowerShell?
Is there a commandlet that works with resources created in the new portal? As with the majority of Azure, the documentation is severely lacking or outdated. Am I doing something wrong?
What are my options? Do I have to delete the Traffic Manager instance and re-create it in the old portal? Recreate it in PowerShell?
Thanks for your assistance.