I have an asmx webservice that is hosted in azure cloud and it has been active for the past 2 years and recently I have received an email from Microsoft stating that
"Azure App Service resource management will now be supported only
through Azure Resource Manager. Support through Azure Service
Management will be retired on June 30, 2018. Transition to Resource
Manager to keep programmatically managing your resources."
Dear Azure customer, You’re receiving this email because you’re a
current Azure App Service customer, and you use an Azure Service
Management–based client to programmatically manage your App Service
resources.
The Resource Manager portal and APIs have replaced the legacy Service
Management portal and APIs for managing App Service resources.
Beginning June 30, 2018, App Service resources will be supported only
by Resource Manager. You’ll no longer be able to manage App Service
resources using Service Management.
Resource Manager offers a number of advantages over legacy Service
Management, including: • A robust resource deployment model.
• Built-in role-based access control. • Fully supported REST API and
clients for existing and new features.
Recommended action
We recommend you transition any automation that programmatically
manages App Service resources using Service Management APIs to
Resource Manager APIs by June 30, 2018. The specific steps you’ll
take depend on what client(s) your automation is coded against. Read
our blog post to learn more about the transition and any action you
might need to take.
I am not sure whether this is a kind of question to be posted here but i thought someone familiar with azure will be able to shed some light on this. Thanks in advance.
Azure App Services were removed from the "old" portal, https://manage.windowsazure.com and can only anymore be accessed from the "new" portal, https://portal.azure.com.
If you got some web app created using the old portal, then you need to managed it using the new portal.
The above email is regarding any customization that rely on the old portal, and its APIs to function. You need to update them to use the new portal, and its API for them to continue functioning after June 30, 2018.
Related
Would you let me know that what is the new feature introduced in the Mar. 11th release for App ID, such as new rest interface etc.?
The new feature referred to is the IBM® Cloud App ID management API.
The management API is secured with IBM Cloud Identity and Access
Management generated tokens. This means that account owners can
specify who on their team has which level of access for each service
instance. For more information about how IAM and App ID work together,
see Service access management.
With the API, you can:
automate the configuration of App ID in your app of your DevOps process.
set and customize capabilities through your app back-end, such as your login widget configuration, sign-up process, and user
management.
See more in this IBM Cloud documentation
I am reading the book Exam Ref 70-532 Developing Microsoft Azure Solutions, published in March 2015. In chapter one, it has a section "Configuring endpoint monitoring", where it gives you the steps to configure endpoint monitoring using both the Classic Management portal and the Preview portal.
Following the steps given, I am able to set up endpoint monitoring via the classic portal.
However, I cannot seem to do this via the new portal.
Here are the first two steps listed in the book:
Navigate to the blade of your website in the portal accessed via
https://portal.azure.com
Scroll down to Monitoring and click Webtests.
I cannot see any reference to "Monitoring" or "Webtests" on the azure portal for my website.
Has this functionality been removed from the preview portal?
Is there any way to configure endpoint monitoring via the new portal?
Web Application Endpoint Monitoring has been removed from Azure since October 31, 2016.
The new, replacement functionality is Application Insight Availability Tests
See this link for an article about migrating from Endpoint Monitoring to Application Insight Availability Tests.
These are also available in the Application Insights->Availability
I have a Azure benefit from my Visual Studio with MSDN subscription.
Microsoft doesn't host MySQL servers in Azure, but I can create a DB from ClearDB through the Azure Portal.
Questions
Is this services included in my benefit?
Can I "Buy" a custom domain with my benefit?
You can provision a VM and deploy MYSQL, this would be included in your benefit but maybe expensive.
You can provision SAAS services like ClearDB via Azure Marketplace but generally billing is separate. When you provision a third party service there is normally a FREE TIER available. If moving to a PAID TIER generally this is billed separately from your Azure Payment methods I have found. Point being , depends on the service you are provisioning. Best bet is to ask the service provider sales channel.
What is the difference between these two portals and why? And when should I use which of them?
For example:
When I want to configure if/which Java version I want to use in a WebApp, in the "manage"-portal I only can choose between off and v1.7.0_51. In the "portal"-portal I can choose between off, v7 and v8.
Or, if I want to create a new Ubuntu-VM, in the "manage"-portal I can choose between v12.04, v14.04 and v15.04. In the "portal"-portal there is only v14.04.
As commented by Mike, manage.windowsazure.com is the current production Azure Portal while portal.azure.com is the preview portal which will eventually replace the production portal.
From an underlying technology perspective, there's one big difference between the production and preview portal. Production portal makes use of Azure Service Management API while the Preview portal makes use of Azure Resource Manager (ARM). Along with ARM API, you get Role-based access control (RBAC) that enables you to grant granular permissions on your Azure resources to your team members. In the production portal, there's only a concept of Subscription Administrator and Subscription Co-Administrator.
Not all services in Azure has been ported to make use of ARM API as of today and that's why you see only few services in the preview portal. Services that make use of ARM API (all the new services) will only show up the preview portal.
As to when to use what portal, just see the Azure services you need to manage. Based on how they can be managed, you will choose between production and preview portal. Also please note that functionality for a service may differ between portals even though it is present in both portals. That may be another criteria between choosing the portal.
More information Can be find from microsoft site
Azure Resource Manager vs. classic deployment: Understand deployment models and the state of your resources
It looks that the list of services I can deploy with resource template manager for Azure is limited. I see examples for VM, Web Sites, Storage, SQL, but not Cloud Services.
Does anyone know if I can use it for Cloud services (web roles, worker roles)?
This has been mentioned on the User Voice forum for Resource Manager HERE.
It has recently been updated to be a "planned" feature as of June 25th. Feel free to add your votes to the feature request!