I have a newly created Azure Cloud Service. A sample project has been deployed and everything is working fine.
I now need remote desktop access to the service. After enabling Remote Desktop connections through the Azure Portal, downloading and running the generated .rdp file in windows I get the error:
An authentication has occured (Code: 0x80004005)
From windows Remote Desktop.
Signing information has been checked and double checked, same result on multiple computers.
So, steps taken:
Created Cloud service with roles
Enabled Remote Desktop through the Azure portal
Downloaded and run .rdp file
Has anyone else experienced this and/or have any solutions?
So I found the solution.
When enabling remote desktop in the Azure portal, I had chosen a username that was not my email.
If I use my Azure account email as username, everything works perfectly.
After testing, in fact any email will do.
Related
I have an Azure Virtual Desktop environment with a host pool and a single session host for testing before being roled out to production (with more session hosts). The session hosts are joined to an AD DS domain and the domain is in sync with Azure AD for both users and devices.
I am using Azure File Shares and FSLOGIX for user profiles which is working perfectly.
I am currently working on setting up several applications with MSIX and I believe I am 99% there. One of the applications I have setup is Notepad++ and when I run the notepad++.msix application from my test machine it works. I have then converted the MSIX to VHD and I can mount the VHD manually on my test machine and the app runs without issue.
Now here is where it goes wrong. I uploaded the MSIX app (the VHD) to the Azure file share and linked it to the host pool and app group, however when I login to the session host the VHD doesn't attach automatically so the app never appears for the user. When I manually mount the VHD I can run the app without issue.
The difficultly I'm having is that there are no errors at all, not even in event viewer. So I am not sure why it won't automatically attach the VHD.
At first, I thought it might have been permissions. but doesn't seem to be the case, the computer account and user account are both SMB contributors in RBAC on the share and have read/execute/list at the NTFS level.
Anyone seen this and know where I could be going wrong?
Thanks
Jon
To resolve the issue I was having, I had to make sure that the VM extension that runs the PowerShell script to join the session hosts to the host pool, I needed to use the latest URL which at the time of writing was and it allows MSIX app attach to work correctly.
https://wvdportalstorageblob.blob.core.windows.net/galleryartifacts/Configuration_09-08-2022.zip
I'm trying to publish an asp.net core app from Visual Studio 2022 to an Azure App Service using Azure AD Microsoft Identity Platform for authentication. At the Microsoft identity platform screen, its showing an error:
Failed to add password. Unable to save changes because the credential
limit has been reached. Please delete a credential and try again.
I'm not seeing where I can "delete" credentials. I'm also not sure if this is from my Azure App Service, or local machine. I searched my App Service on Azure, but couldn't find anything related to this.
Any ideas?
We have tested this in our local environment it is working fine, Below statements are based on our analysis.
We have created an Asp .Net core (in Visual Studio 2022) with managed identity as an authentication type in our local environment.
I'm not seeing where I can "delete" credentials.
I'm also not sure if this is from my Azure App Service or the local machine. I searched my App Service on Azure, but couldn't find anything related to this.
Before publishing the project, if you are configuring the Microsoft identity platform then you see an option to store the secrets in our local environment as shown below.
If you want to list those secrets in our local machine
Run the following command from the directory in which the project file exists:
dotnet user-secrets list
Here is the sample output for reference:
You can refer to this documentation for more information about Safe storage of app secrets in development in ASP.NET Core
If you want to configure the Microsoft identity platform at the time of publishing you will get an option to store this client secret as Azure App setting
As shown in the above GIF, while creating the secret from vs you will select the app registration to which this client secret needs to append.
Once the client secret got created you can check the secret value in the portal by routing to Active Directory > App registrations> select app registration Name(that you choose while creating from vs) >certificates & secrets.
you can delete the secret/credentials from there.
I have developed an app service in Microsoft Azure and am working on it. Now I want to download my source code from the Azure server to my local machine. I have tried using FTP but I am unable to establish a connection.
I don't know what I'm missing from this link: https://medium.com/#michaelhenderson/how-to-download-your-source-code-from-azure-app-service-59c848752b0f.
Can anyone help me out with the issue?
Thank you.
There could be several reasons for the FTP issue, the exact error message may provide some pointers.
Azure App Service supports connecting via both Active and Passive mode. Passive mode is preferred because your deployment machines are usually behind a firewall.
Kindly check this document: https://learn.microsoft.com/azure/app-service/deploy-ftp#get-ftp-connection-information
Alternatively, you could copy files directly from Kudu console to local: http://yourwebappname.scm.azurewebsites.net/
(append ‘scm’ to the default WebApps emphasized above)
Navigate to cmd button and you can find your project files under site/wwwroot folder
Also, you could clone the WebApp from Azure App Service to your local Visual Studio (VS) by using VS team explorer.
I want to download ADLGen2 file to my local server using ADF.
I tried to set up self hosted integration run-time, but I am getting below error
the integration runtime (self-hosted) node has encountered an error during registration
The account through which I have logged into my azure portal and the account which has access on my local machine are completely different.
Azure Portal login : xyz_abc#gmail.com
Local machine login: officiallogin#companyname
Is the issue because of 2 completely different logins
Can you please let me know how to resolve this issue.
Thanks,
Raksha
When you say "The account through which I have logged into my azure portal and the account which has access on my local machine are completely different", make sure to uninstall and re-install the self-hosted integration runtime manually choosing the option2.
OR
You may try to uninstall the current self-hosted integration runtime. Maybe you can try the Option1. It will install and register the integration runtime automatically.
Reference: Create and configure a self-hosted integration runtime.
So I setup TFS continuous deployment and I'm running into a situation where my build compiles just alright but fails in the deployment phase when communicating with Azure. My log looks like
Get Default Azure Cloud Service Publish Profile
Set Project to build CSPack
Run MSBuild for Project
Run Visual Studio Test Runner for Test Sources
Publish Output
Deploy application to Azure
8/23/2012 7:20:04 AM - Preparing deployment for rcfoapi with SubscriptionID: mysubscriptionidhere.veryverylong.andkeepsgoing...
8/23/2012 7:20:04 AM - Connecting...
An attempted http request against URI https://management.core.windows.net:8443/mysubscriptionidhere.veryverylong.andkeepsgoing
/services/hostedservices/myrolenamehere?embed-detail=true
returned an error: (403) Forbidden.
Additional Exception Information:
Error Code: AuthenticationFailed
Message: The server failed to authenticate the request. Verify that the
certificate is valid and is associated with this subscription.
Typically, a response of (403) Forbidden from a Windows Azure
Management API means that the X509 certificate used to
authenticate the call is not valid. The certificate may have
been revoked or expired. Reconnect your Windows Azure
subscription to your Team Foundation account.
I tried the 'Disconnect from TFS' link in the Azure portal, then verified that the certificate in the 'certificates' section of the Azure portal. I confirmed using the fingerprint hash that the same certificate is also in my local computers' certificate store ('my' store). Then I relinked TFS back via the Azure portal.
But I still get the same error. Any idea?
Update:
I also tried a few additional steps, nothing seems to be working :(
Deleted the entire cloud service
Created a new cloud service (with same name)
VS2012 deployed to the cloud service on both production and staging (because I need to service operational for front use and back testing)
Verified the Windows Azure Tools certificate in the portal's cloud service 'certificate' section (which matches my local copy). I understand this will be different from the one between TFS and Azure
Went to TFSPreview.com => top left gear => project administration => services => no linked services seen
Went to user profiles => connections => OAuth connection listed (MANAGE-PROD CLOUDAPP by Windows Azure) => removed it
Within the Azure portal, linked the newly setup cloud service back to TFSPreview.com
Locally in VS2012, disconnected TFS ('team' => 'disconnect')
Locally in VS2012, logged out of TFS ('team' => 'connect' => 'sign out' at the bottom)
Signed back into TFS, connected to the team project
Made a trivial change => check in => triggered continuous deploy
=> Same error as before :?
Thanks
TFS Preview is not using the same cert you have on your local dev box. When you connect the accounts Azure gives TFS a different cert and it is possible that is the one that has expired or is no longer there. If you have multiple projects connected to Azure the only option is to go into the admin site on TFSPreview (the gear in the upper right) and disconnect all projects that are connected to that subscription and then rerun the connection wizard. This will ensure we get a new valid certificate for your azure subscription. When you reconnect the subscription to the project we will find the existing build definitions and not create new ones.
I had the same issue and for me the solution was to renew the certificate. See here: http://support.microsoft.com/kb/2780289
This can happen if your certificate needs to be renewed in the Azure control panel.
It can also happen if you don't have a staging or production environment deployed first. I'm not entirely sure why since it deploys a new one, but this fixed the issue for me just now.