I created a program and deployed it into the Windows Azure Portal but now I want to change the account that it is associated with but it won't let me. Is this possible and if it is could someone point out how to do it because I can't find a way so far. I created a web service that held data that is consumed by a client and I want to change the associated Windows Azure Account but it keeps trying to publish the service onto the account I used to begin with instead of the new one, even when I sign into my new windows azure account. Using VS to publish the service to the portal
Thanks.
Related
I have Windows service created with C#, but this service is working good when I start manually.
If I want to set automatically start, this service not work correctly.
If I want to login with my account this service not work.
I have installer in my project.
What can I do?
I have access to my Azure AD Portal. I also have an external ASP.NET application which is accessing the Microsoft Graph API. For this purpose I add an App Registration which give me an Application ID and Key to be able to configure my ASP.NET application to authenticate itself against the Graph API.
I need the my ASP.NET application to read groups out of Azure AD. I can authenticate successfully but I get an error saying that I have not enough privileges. Then I go back to the Azure Ad Portal and add permissions to the App Registration I added. This works ok so in the end I have the Graph API response on my ASP.NET application.
Now it comes the issue. I selected too many permissions so I want to use the smallest set of permissions that are necessary for my ASP. So I go the Azure Portal AD again and remove some of the permissions. When I test my app again, I still receive the groups even if I have no permissions selected.
I think this is an issue. Or there's some kind of delay? I don't think so because when the API is working and has the proper permissions I can add a group in Azure AD Portal and instantly see it in my ASP.NET application.
This issue is specially annoying because you can't really test the permissions your app needs.
Thanks.
I have a web application that currently runs on Azure under my own Azure subscription. I'd like to transfer this to another party so that they can run the web application under their subscription. How can I do this?
Can I:
Give them some sort of package that they can publish (ideally I'd like to avoid giving them the actual source code), or
get connection details from them so that I can publish directly from Visual Studio to their subscription (said connection details would have to not give me full control over their subscription)?
Note that the web application consists of a website, an Azure SQL database, and a Blob container.
The best method would be for them to provide you the publish profile that they can download from the Azure web application dashboard.
This provides you a file you can import into your project that will publish to that Azure subscription. The information contained in the publish settings file is a unique userId and password to that web application only (you can open the file with Notepad and read its contents).
If you need to interact with the database directly, you will need the SQL username and password as well as they would need to open the SQL Azure firewall to allow your IP address to connect to it.
Interacting with the blob container could be done using the Blob APIs (or some of the various GUI tools out there) and a key with the proper read/write accesses attached to it.
Azure now has the Resource Manager API (ARM). One of the features: Resource Groups. A resource group serves as a bounding box for a set of resources (web apps, VMs, etc.). You can grant permissions on a resource group, allowing someone external to your subscription/organization to work within that resource group. With owner permission, they'd be able to create new resources within that group, and never be able to see anything beyond the resource group.
Microsoft's Azure Mobile Web Services lets you download a .NET or JavaScript Service and a client that talks to the Service. These are written in C#, or JavaScript. I chose to get one in C#. There is are several parts in the generated solution
A Windows 8.1 desktop client (yourname.Windows)
A windows mobile client (yourname.WindowsPhone)
A Azure Mobile Web Service (yournameService)
A shared .net assembly named (yourname.Shared)
You can right click on yournameService and click Publish and it takes you through a wizard which publishes your application directly from Visual Studio to an Azure server. At some point in the wizard it establishes automatically some rather complex credentials (because you have already logged into an Azure web subscription). Generally you can just click Next, Next, and get it published.
Now you have a webservice, which opens up in your web browser, but which requires you to log in. What I want to know is, how do you know the user name and password used for this login?
http://yourapp123.azure-mobile.net/help
Then you click "Try it out", and a web browser authentication dialog pops up.
Why is this a problem? So far as a user I have input:
My Visual Studio login credentials,
My connection to Azure (perhaps same, perhaps different as visual studio login)
During wizard I've determined login credentials to publish to Azure, using values I have no idea where they came from, and so I left them alone. These seem to be the only credentials I had any opportunity to enter, and any change from the defaults renders the wizard inoperable, so I'm sure that's not where I enter my user and password.
I created a username and password when I created the Mobile WebService, and these do NOT work when I try to log in.
Leave the user name blank. And put in your application key as password. You can find your application key from your Azure portal > Mobile service > manage keys.
The reason being is that AMS uses a Zumo header to decide proper authentication. Which is what the application key is used for. So it's making sure only people or applications which has the application key can access the web service. Hope this helps.
I created a Cloud Service project containing an MVC Application in a Web Role, and a Worker Role. In the MVC project, I am using Windows Authentication...and certain fields are managed based on the user being authorized (no biggie).
When I "Set As Startup Project" to the MVC project, my Windows Identity Principal comes across fine...and everything displays & works as expected (which is good).
Then, it becomes time to work-on & debug the Worker Role. To do so, I must run the Windows Azure Emulator by choosing "Set As Startup Project" to the Cloud Service project itself (and then pressing F5). Doing so fires-up all the Cloud Service roles within the Windows Azure Emulator.
However, when I do this the IsAuthenticated property is false...and all my HTML elements disappear.
QUESTION(S):
- Why does running the Windows Azure Emulator locally prevent Windows Authentication?
- If I need to "setup" the emulator...how?
PORTION OF THE SERCURITY CODE:
Nothing special here...
var identity = filterContext.HttpContext.Request.LogonUserIdentity;
if (!identity.IsAuthenticated)
RedirectToAccessDeniedPage(filterContext);
PORTION OF THE WEB CONFIG:
Nothing special here...
<authentication mode="Windows" />
<identity impersonate="false" />
When you setup the MVC project as the startup project, you are essentially running the project locally on your machine through IIS. IIS will automatically use your current NT credentials as the currently logged in user, which makes sense.
As hinted by Parv Sharma in his comment, when you set the cloud service as the startup project, a separate VM emualtor is started, simulating what would happen in the cloud. Although the VM also runs your application in IIS, it has no idea who you are since you haven't logged in yet. And because your local NT credentials are not stored in that VM (and it doesn't make sense to store user credentials in a VM regardless), IIS doesn't recognize you as being logged in.
So you will need to implement a form of authentication form that will allow users to authenticate against a Directory Store, which is what Azure Directory Services is all about. Here is the MSDN documentation for Azure Directory Services scenarios which contains a link for a sample implementation.