Product: EvOps for Azure Stack
Release Date: 2017-12-15
Content: New Features, Corrections, Known Limitations
EvOps for Azure Stack
EvOps for Azure Stack delivers a seamless and cloud-ready service catalog, customer support and event-driven workflows on Microsoft Azure platforms, elevating organizations to deliver great IT operations for hybrid clouds.
The following features have been added in this version.
UX improvements in SKU Picker editor
Office 365 extension now supports outbound email
The following defects have been corrected in this version.
Validation did not work in “create EvOps account” blade if resource provider was not pre-registered on subscription
Validation did not work in “create Request” blade if resource provider was not pre-registered on subscription
The following limitations have been identified in this version.
EvOps is currently not supported on integrated (multi-node) systems.
Workaround: Start evaluating EvOps on the ASDK, design and build your request templates which can later be exported and imported into your multi-node environment.
When creating a new EvOps account, you might see a message saying, "Checking permissions to create a Run As Account in Active Directory". If this happens, it should be ignored. The text is incorrect, EvOps does not try to create a service principal automatically for you in your directory. If we implement this automation later on, to simplify the process of creating an account, we will prompt and ask first. We do place the provided service principal in the contributor role of the subscription where you create the EvOps account, this is currently a requirement.
Workaround: Ignore message and create the account.
It is currently not possible to edit list values like "Classification, Source, Support group". This will be possible in a future release.
After adding an extension and the success message is shown, it can still take a while before the extension shows up in the list of active extensions.
When modifying extensions in EvOps on the ASDK, you can experience delays and "locks" in the UX. This is due to the single VM setup and should not be expected in a production environment.
Subscriptions should not be deleted before deleting the resources of those subscriptions first. If the subscription is deleted without doing so, it will leave orphaned resources in the system. This is a known issue in current builds of Azure Stack.
Resource group- and location picker are added by default to the wizard of a new request template. For any request that does not include a Deployment Activity, the resource group and location picker can be removed.
Want to obtain a copy of the latest download link? Contact our Sales department at firstname.lastname@example.org and we will assist you!