Great event, besides all other sessions check out session 7 if you would like to learn more about identity and access management 😉
Press the boost button – what a workspace aggregator should do for you!
While “workout boosters” with impressive names are much talked about in sporting circles, they are mostly ineffective; “workspace boosters”, on the other hand, are real winners. And why would you need such “workspace booster”? The answer is simple: to help you master the transformation of the modern workplace into the workspace, cost-efficiently and with quite some productivity gains.
Obviously, the workplace 4.0 era has already been initiated, and it is characterized by variety and multiplicity:
- Multiple devices – People work with traditional PCs as well as laptops and mobile devices Already today, the average employee uses at least three devices and works in a multi-device environment.
- Multiple applications – People work with any kind of applications, from traditional, physically installed applications to SaaS apps and mobile applications, with web and SaaS applications enjoying particularly high growth rates.
View original post 470 more words
The Azure Costs Team is happy to announce the launch of the new support for Azure Rate Plans & Pay-as-you-Go subscriptions. After an extensive beta together with many interested users, we are now ready to make this new feature globally available for everyone.
This feature completes Azure Costs and allows you to manage any subscription type and pricing model that Microsoft offers in the different regions for the Azure cloud.
Interested in managing Azure Rate Plans or Pay-as-you-Go subscriptions?
Try the new subscription support today by simply logging into your Azure Costs service. We also designed new plans explicitly for our users without an Enterprise Agreement. Customers who are currently using a payed plan, can connect additional subscriptions for free.
Any questions, wishes or ideas? Try our feedback portal or drop a mail to email@example.com.
The azure costs team is pleased to announce the support of more payment options, which goes live today. From now on, you are able to pay with all major credit cards, e.g. Visa, MasterCard or American Express. In addition we support Paypal as a very comfortable way to pay as well.
The payment is processed from our partner FastSpring who is one of the most reliable and successful payment providers in the world.
You stay in control and can upgrade or terminate your subscription at any time directly in our billing portal or in your FastSpring account.
Thanks to your feedback, we were able to constanly improve the Azure Costs user interface in the last weeks and months. One special hint we got from you, was the fact that it sometimes can be pretty confusing, when it comes to multiple Microsoft and Azure Active Directory accounts.
As we’re continually deploying additional features that you have been asking for to azure costs and here’s a small but very useful new functionality:
From now on, you’ll get the mail address that was used for logging into Azure Costs, whenever you move your mouse cursor over the avatar. This ensures, that you’ll never be confused anymore about different accounts or dashboards without data.
Interested in the feature?
Try the new feature today by simply logging into your azure costs service and move the mouse cursor over your avatar. The feature is part of plan it doesn’t matter if you are using the Basic, Professional or Enterprise plan.
Disclaimer: This article is about Visual Studio Team Services (VSTS) and GitHub. The author has a very positive opinion about both services and does not get any offers from Microsoft or GitHub writing this article. The whole article is written IMHO.
Over the last years GitHub has become a success factor for projects related to git repositories for me personally. I also tested several other solutions but mainly I struggeled with the performance or the usability. About 2 years ago I started using Visual Studio Team Services (VSTS) with a work related project. The service looked promising but had a lot of early release issues, so in the last 24 months it was interesting to see how a promising solution became adult. Last week I decided to move away from GitHub for all my closed source projects and rely on Visual Studio Team Service (VSTS). This article gives a deeper look on the main reasons of why I did the move and may help deciders to get detailed information before implementing:
Nowadays thanks to bower, npm, bundler or NuGet the amount of Git repositories are growing steadily. When you are focused on component based software development Git is a great helper but the amount of repositories is sprawling because very often every component has its own live in a separated Git repository, which means you have a separate release cycle and a different versioning compared to your main project.
I guess this is the secret source of component managers which are working closely together with git repositories. Of course VSTS and GitHub are supporting multiple git repositories but GitHub lets you pay on a package on git repositories, VSTS lets you pay for users. Especially for small teams paying for users is the better deal, compared to paying for repositories. At the end Microsoft offers a smaller groups of 5 everything for free. This fact stopped my permanent GitHub problem: Having too less private repository space.
O – Allows to have as many GitHub repositories as needed
+ – Generates releases out of tags automatically (good semver integration)
– – Charging base is the count of private git repositories
O – Allows to have as many GitHub repositories as needed
+ – Comes with unlimited git repositories, plans are user based
– – Repository management is not that intuitive as it is in other solutions
Pull Requests and Forks
Forks and pull requests are the most important features GitHub introduced very early to support community driven development. I would say in the open source world Github is the platform when it comes to forks and pull requests. Currently I would never think about moving open source repositories away from GitHub because of this great feature.
When it comes to closed source projects, forking and pull requests are becoming only important in bigger teams with different products or product lines. We are using this feature strongly in our teams at my company. Smaller startups or teams will not use these workflows often but nevertheless it is a road blocker for me to do the 100% switch to VSTS. I guess it took Microsoft around 12 month to deliver it in a more simple way GitHub is doing this.
+ – Cross repository forking
+ – Pull requests incl. discussion thread and a lot of community features
O – Supports pull request on repository level
Agile Process support with EPiCs, features and backlogs
When it comes to bigger teams or more structure, people are having the option that to implement a process is the key. This brings me to the biggest enterprise blocker I see in GitHub, the Issue-Tracking system. Companies who migrated to an agile framework like SCRUM or KANBAN need to have the option to work with features, backlogs or bugs. Microsoft delivers with VSTS a highly customizable and adaptable work item management system. The SCRUM and KANBAN template makes perfect sense for agile teams but also the traditional waterfall model can be implemented (even if I don’t understand why someone should do this.)
– – It’s just an Issue Tracker
+ – Has good integration into many cloud services
+ – Offers customisable work item management
+ – Comes with templates for agile team structures
Handle your Test-Cases
Even if your projects comes with a great code coverage and good unit tests, the requirements to execute manual tests or just to orchestrate automated integration tests exists. VSTS implements based on the work item management a test case management which has the option to integrate it with automation bots via WinRM and other protocols.
The ability to document test cases and write specific step by step guides how to verify a feature is a big plus esp. in small teams where no dedicated QA resources are hired.
O – Ability to integrate with external QA services
– – No integrated test case management
O – Ability to integrate with external QA services
+ – Test Case management is part of the work item management
Centralised Source Code management as migration path
For a couple month Microsoft offers virtual TFS collection, which allows companies that want to go pave the road for git based repositories to stay with the existing centralised source code management besides new git repositories. In the early day VSTS just supported a TFS collection per project space but now maintaining TFS collection is that easy as it is creating new git repositories. This will become very important features for existing TFS customers.
Revised Build-System incl. Linux Support
I guess Microsoft learned very fast that the XAML file based build system was very inflexible and complicated for a SaaS service like VSTS. Because of that a couple month ago a new step based build system was introduced which will orchestrate the build agent out of VSTS
Since Microsoft supports Windows, Linux and Mac build agents there are no road blockers anymore, besides that the hosted build services for VSTS are very rare. There is a build server Microsoft offers out of the box but from my experience you will get more problems customizing that. When you are focused on Azure check also what the Azure App Services can do for you because KuduSync offers out of the box build for your .NET application during deployment.
+ – Many different build services available with GitHub integration (CodeShip, T..)
– – Build definitions are not part of the code project
– – No release management to aggregate several projects
– – Hosted build services for VSTS rare
+ – Build definitions are part of the code project
+ – Release Management allows to aggregate several sub projects
Other services and options:
There are also other options and products on the market and I guess one of the most popular one is Assembla which is pretty comparable to Visual Studio Team Services. Also the products from Atlassian (Jira, BitBucket) are great options supporting your development cycle. This article had the intention to support companies who are dealing with GitHub and / or On Premise TFS and now are thinking about combining the positive of both.
I personally think GitHub could become a great option for enterprises as well, when the Issue-Tracker problem is solved which was mainly the reason why I searched for an alternative!
The azure costs team is pleased to announce the launch of the team admin notification support.
The new feature enables team managers and administrators to get notified when a team member activates his account. A team administrator gets a message when a user accepts the invitation or is joined automatically when accessing the service via Azure Active Directory account.
How to get started?
The team administrator notification feature is part of every enterprise subscription. Enabling the notification in azure costs is this simple:
2) Select “Manage Team” in the drop down on the avatar and open the newly introduced settings page.
3) Just switch the notification on with the displayed checkbox:
Interested in the team notification feature?
Try the new feature today by simply logging into your azure costs service and migrate to a team account. The feature is part of any enterprise plan and part of any trial.