[英]manage.windowsazure.com vs. portal.azure.com
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 . 例如:当我想配置我想在WebApp中使用的Java版本时,在“manage”-portal中我只能在off和v1.7.0_51之间进行选择。 In the "portal"-portal I can choose between off , v7 and v8 .
在“门户” - 门户我可以选择off , v7和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 . 或者,如果我想创建一个新的Ubuntu-VM,在“manage”-portal中我可以选择v12.04 , v14.04和v15.04 。 In the "portal"-portal there is only v14.04 .
在“门户” - 门户只有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. 正如迈克评论的那样,
manage.windowsazure.com
是当前生产的Azure门户,而portal.azure.com
是预览门户,最终将取代生产门户。
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)
. 生产门户使用
Azure Service Management API
而预览门户则使用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. 与ARM API一起,您可以获得
Role-based access control (RBAC)
,使您可以向团队成员授予Azure资源的细化权限。 In the production portal, there's only a concept of Subscription Administrator
and Subscription Co-Administrator
. 在生产门户中,只有
Subscription Administrator
和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. 并非所有Azure中的服务都已移植到今天使用ARM API,这就是为什么您在预览门户中只看到少量服务的原因。 Services that make use of ARM API (all the new services) will only show up the preview portal.
使用ARM API的服务(所有新服务)只会显示预览门户。
As to when to use what portal, just see the Azure services you need to manage. 至于何时使用哪个门户,只需查看您需要管理的Azure服务。 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 更多信息可以从microsoft站点找到Azure Resource Manager与经典部署:了解部署模型和资源状态
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.