Visual Studio Enterprise suscription & azure? - visual-studio

I have a Visual Studio Enterprise suscription and they show me that i have 150$ credit on azure.
Is there anyway i can use some of the azure services through my suscription?
if yes how?
Thank you

Yes, you may use Azure offerings using your monthly $150 credit.
The only thing that I have come across that I can not use it for is for SSL Certificates.
When you create a new Azure resource be sure to select your subscription that you have the credit on.
Please note the following from Microsoft.
The monthly Azure credit for Visual Studio subscribers is for development and testing only and does not carry a financially-backed SLA. We reserve the right to suspend any instance (VM or cloud service) that runs continuously for more than 120 hours or if we determine that the instance is being used for production. We are making this capacity available to Visual Studio subscribers on a best efforts basis; there is no guarantee of capacity availability.
For up to date details on what you can use it on see this link.

Related

How does one associate Visual Studio subscriptions with a company Azure subscription?

I have a Visual Studio subscription.
I'm trying to implement Application Insights in a Web API application in Visual Studio.
The wizard is trying to associate AI with my Visual Studio subscription. Rather, I want to integrate with my company's Azure subscription.
So, how is this done? Do I have to contact the Azure admin and add me to Azure? I have seen responses like "add you as a co-administrator". This is pretty dumb, when you're a developer.
Our company Azure subscription has Active Directory integration. So what. How do I register with the company Azure subscription that I want to implement services as a developer in the company??
Can someone provide some insight or references? The documentation is ponderous on this point.
If I understand your question correctly, you need to obtain an Instrumentation Key from a resource that is created in your company's Azure portal. Then, you can install application insights in your project and use that instrumentation key.
If, on the other hand you are asking why you have to be a co-administrator then you are correct. This was the case for a while but not anymore.
Account admin can now assign new users to specific resource groups. Each resource group can contain one or multiple resources. Read more: https://learn.microsoft.com/en-us/azure/active-directory/role-based-access-control-configure

Visual Studio Online and Local Build Host

We have visual studio online professional license and MSDN, we need a local build server as we require third party controls. Can anyone tell me the licensing on this? Do we need to purchase a local TFS license as well?
No additional software needs to be purchased to setup a build environment with VSO.
If you want to setup a Xaml build controller the easiest way to get that is to download and install but not configure TFS Express which is free and does grant you a license to use the software. Once that is done you can simply launch the admin console and configure the build controller against your VSO account.
With the new build system you simply download the agent software directly from VSO in your account control panel. You can find documentation here https://msdn.microsoft.com/Library/vs/alm/Build/agents/windows#ManuallydeployabuildagentDownloadandconfiguretheagent
Each account allows you to connect 1 Xaml controller or 1 agent for free. To connect additional agents you need to purchase more Private Agents you can see details on pricing here https://www.visualstudio.com/features/continuous-integration-vs and here https://www.visualstudio.com/en-us/get-started/setup/get-more-build-or-load-testing-vs
If the MSDN subscription account you have is one of the followings, you can download and deploy one instance of Team Foundation Server 2015 from MSDN subscriber download site, and you get one CAL(Client Access License) as well.
Visual Studio Enterprise with MSDN
Visual Studio Professional with MSDN
Visual Studio Test Professional with MSDN
MSDN Platforms
However, for example, if you want to have 2 build servers to associate with VSO, you have to buy another one license for TFS (TFS license includes build service); similarly, if you want to allow 10 users to use the build server, you may need to buy CAL license based on the TFS license you have (for example, Team Foundation Server 2015 purchased in retail channels contains up to five CALs)
Please check the license white paper for the details: http://www.microsoft.com/en-us/download/details.aspx?id=13350

Can you run Windows Client VM's on Azure with an MSDN Operating Systems subscription?

I have spent hours attempting to answer a very basic question about Azure and MSDN. Microsoft documentation and support is very poor (and their pricing very high), but because I must continue to develop applications for Windows as a contract developer and I wish to have a backup and test development machine, I have no choice but to submit to their requirements.
I would like to answer what I think is a simple question: If I purchase an "MSDN Operating Systems" subscription (as opposed to a "Visual Studio Professionl with MSDN" subscription), will this enable the "Windows Client" VM option on Azure? Or, am I required to purchase the much more expensive "Visual Studio Professionl with MSDN" subscription in order to have the Windows Client VM option in Microsoft Azure?
Note that the "feature comparison" between these two MSDN choices here has no bullet point in the "Microsoft Azure" line-item for the "MSDN Operating Systems":
... However, this could just mean that you don't receive any monthly credit for Azure usage - not that the Windows Client VM is not available for this Azure-MSDN connection. But then again, maybe my fear is correct - that the Windows Client VM option will not be available on Azure, even if I pay for the MSDN Operating Systems subscription.
As I've noted, after literally hours of trying to answer this question, I can't (the Microsoft references are useless).
Can you run Windows Client VM's on Azure with an MSDN Operating Systems subscription?
This post http://azure.microsoft.com/blog/2014/05/29/windows-client-images-on-azure/ states that the following MSDN subcriptions qualify for Windows Client VMS for dev and test:
Visual Studio Ultimate with MSDN
· Visual Studio Premium with MSDN
· MSDN Platforms
· Visual Studio Test Professional with MSDN
· Visual Studio Professional with MSDN
So it looks like the answer is no.
Tim

Can't sign in to Azure to publish with Visual Studio 2013

I'm trying to test Azure by publishing a basic web app. After signing in to Azure from Visual Studio, I'm met with the following message:
Sorry but we didn't find any Windows Azure subscriptions associated with your account.
You can sign in with a different account or sign up for a Windows Azure subscription.
I use Windows 8 with an attached ecu account, and have signed up to a trial Azure account under the same credentials (which I can log in to normally fine).
Results[1] from a similar problem suggest the accounts are mixed up, and to contact an admin with the ticketing system to rectify[2]. However selecting "Having issues with sign in or signing up for an account?" links me to a page, which quickly redirects me to another broken page and I am unable to proceed.
What is the best course in action in either:
publishing the app to Azure
contacting Microsoft about fixing my trial Azure account
Thank you
[1] http://social.technet.microsoft.com/Forums/en-US/1b61b9a9-e763-4893-acc1-aa60a7d0b03d/msdn-subscriition-free-access-to-windows-azure-cannot-setup-account?forum=windowsazurepurchasing
[2] http://azure.microsoft.com/en-us/support/options/
Found the answer on social.technet.microsoft.com
I found this article first, so I hope this helps others that find this before the MS article.
https://social.technet.microsoft.com/Forums/azure/en-US/40ac7a3d-12f0-47c5-9cee-97dd5867ddf0/unable-to-sign-in-when-trying-to-publish-web-role-to-azure?forum=windowsazuredevelopment
I know this is an old thread, but I was recently having a problem with visual studio 2015 where I could not sign in to Azure. I came across this SO entry. It was not helpful, but I eventually did find the answer.
The answer was to repair Visual Studio. It takes awhile to run but once it finished I was back in business with Azure in Visual Studio.
https://msdn.microsoft.com/en-us/library/aa983433%28v=vs.90%29.aspx?f=255&MSPPError=-2147217396

How to get Microsoft CRM for Development Purposes?

I am a recent graduate, who has done some work experience at a company developing/designing Microsoft Dynamics CRM Solutions. I have moved on from there and have no official ties anymore. However, I do see the future in this product and I would like to keep developing solutions and increasing my development knowledge of Microsoft Dynamics CRM.
Taking into account the above and that I have a job in a different IT area. As well as the fact that I am determined to start this from scratch... What are my options?
My intentions for the future(1-3 yrs) is to develop Microsoft CRM 2013 Solutions and hopefully sell to local small businesses.
MSDN subscription or using trial subscription on CRM Online instance or using trial key:
http://www.microsoft.com/en-us/download/details.aspx?id=40341
Or if you want to be a startup, you might be eligible for BizSpark subscription:
http://www.microsoft.com/bizspark/
I think your best bet would be to get an online subscription. Your solution's code should be 100% compatible with the new CRM APIs in the SDK. Running everything from an online CRM solution would ensure it will work. This will also ensure that when the next version is released, you will be ready for it.
Unless Microsoft changes their licensing, this might be your only reasonably priced choice.
Try the Demo Builder:
http://demobuilder.cloudapp.net/unauthenticated-home/#
It's a Wizard base tool that will guide you through the process of setting up an online demo environment.
There are a bunch of templates that you can select from that will give you a good idea of the different scenarios where CRM can be deployed.

Resources