I followed a tutorial here and working fine when running in local:
https://docs.microsoft.com/en-us/azure/active-directory/develop/GuidedSetups/active-directory-aspnetwebapp-v1#configure-your-webconfig-and-register-an-application
When I transfer it in our server, I encountered this error.
Hello,
I'm trying to test Azure AD with multiple domains and am having issues verifying one of the 3 domains I'm trying to use.
Over 24 hours ago I started trying to verify my domain. The TXT and MX records are set and have propagated to the internet (Verified independently with DNS resolvers). Two other domains I own, one at the same domain registrar (Godaddy.com) successfully verified within minutes, but these domains are fairly new and unlikely to have been used with any Microsoft-related services in the past
Can someone please assist me with finding out why this domain cannot be verified? The experience others have had lead me to believe that somehow my domain was once verified for a Microsoft service.
Would it be possible to please open a support case to verify whether it's a technical failure or that the domain was already claimed for another service? I am on a free trial so do not have full support and cannot directly open a ticket
thanks,
James.
Get-MsolUser -UserPrincipalName asif@mydomain.com | Select *
This gives lots of attributes and properties but not SamAccountName. Why? is there a way to replicate the SamAccountName here from AD? otherwise I need to do another query in AD based on UPN to pull SamAccountName. There are 25 thousand users takes 2 days to pull samAccountName using UPN
I can't register a new application in Azure Active Directory.
Learn more: https://go.microsoft.com/fwlink/?linkid=843472. More details: Insufficient privileges to complete the operation..
I'm looking through this documentation https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/use-scim-to-provision-users-and-groups for configuring a non gallery application to automatically provision users from Azure AD to the non gallery app and I don't see anything about how to get OAuth access tokens (OAuth bearer token) from an OAuth authorization server's token endpoint that the non gallery application uses.
Step 7 of "To connect an application that supports SCIM:" states :
which seems to imply you can use a static OAuth bearer token that never expires (which doesn't seem any more secure than having a shared secret between the application and Azure AD) or configure the app to use Azure AD as the identity provider (which I take to mean configure the application to go to Azure AD to validate/verify the OAuth access token).
Questions:
Hello,
Could anyone tell if I could change settings in Azure AD Connect?
For example if wanting to change from Password Synchronization to Federation (on premise ADFS).
Could I just re-run the AD Connect installer and make this change?
Thanks,
romatlo32
Hi
One of our customers is getting this when trying to redeem their Azure Active Directory B2B invite. I'm not sure what to advise the customer so they can speak to their IT team and troubleshoot? Are they running a special federation server if so will it ever work? Is there a setting they can enable?
Hello,
I need to configure Azure AD DS and LDAP, but I alredy have configured AD Connect. I found docs that I just need to run PS script in order to enable NTLM and Kerberos for password hash, but I couldn't find what need to be entered for parameter AD CONNECTOR
NAME and AZURE AD CONNECTOR NAME? Is that Server name / Tenant name or something other?
P.S.
With cloud only users, everything works fine.
Regards,
MCSA, MCSE, MCT, IAMCT Country Leader
Hi,
This is a bit of an emergency...
I have an azure tenant that is having issues with Azure AD Domain Services.
As it is suggested, the DNS server were configured in the Vnet as custom DNS.
However, recently there was a complaint that Internet was not accessible from the Azure hosted VM.
I removed the custom DNS servers from the Vnet and switched to "Default (Azure Provided)" and Internet was accessible. However, I could not log on to the VM using my user@customdomain.com account; only with the local Admin account.
Looking at the Azure AD Domain Services Health, there are 2 Monitor messages:
Message 1:
Backup: Last backed up on Sat, 08 Sep 2018 18:51:57 GMT
Message 2:
Synchronization with Azure AD: Synchronized on Thu, 13 Sep 2018 05:59:39 GMT.
And 3 Alerts
Alert 1:
Name: The managed domain is experiencing a network error
Severity: Critical
ID: AADDS104
Raised: 9/13/2018, 10:44:19 AM
Last Detected: 9/13/2018, 5:02:03 PM
Issue: Microsoft is unable to reach the domain controllers for this managed domain. This may happen if a network security group (NSG) configured on your virtual network blocks access to the managed domain. Another possible reason is if there is a user defined route that blocks incoming traffic from the internet.
Resolution: Refer to the following article to resolve this issue Troubleshooting Alerts - Network Error
Alert 2:
Name: The managed domain has not been backed up for a long time
Severity: Warning
ID: AADDS501
Raised: 9/14/2018, 4:51:57 AM
Last Detected: 9/14/2018, 3:36:16 PM
Issue: The managed domain was last backed up on 9/8/2018 6:51:57 PM.
Resolution: Refer to the following article to resolve this issue Active Directory Domain Services article
Alert 3:
Name: The managed domain is suspended
Severity: Critical
ID: AADDS504
Raised: 9/13/2018, 5:06:11 PM
Last Detected: 9/14/2018, 3:36:16 PM
Issue: The managed domain is suspended due to an invalid configuration. The service has been unable to manage, patch, or update the domain controllers for your managed domain for a long time.
Resolution: Refer to the following article to resolve this issue Active Directory Domain Services article
After doing some research, I was able to ascertain that all 3 ports required for AD Synchronisation (443, 3389, 5986) are defined in the incoming rules of the NSG.
From the Monitor message, the synchronisation was done but the backup was not done for less than a week (if you compare the 2 dates between the backup and the sync).
Apparently, according to https://docs.microsoft.com/en-us/azure/active-directory-domain-services/active-directory-ds-suspension, if the issue is not resolved, the managed domain is at risk of being deleted in less than 15 days.
Of course we would like to avoid this but it seems that the only way we can get this resolved is by having the domain controllers backed up. BUT HOW CAN WE DO THIS!!!?? This is an Azure AD DSmanaged domain.
The same above-mentioned article says the following about a managed domain that is in a "suspended" state:
A managed domain is put in the Suspended state for the following reasons:
Managed domains are suspended when Microsoft is unable to manage, monitor, patch, or back up the domain on an ongoing basis.
What to expect
After you resolve the alert, your managed domain goes into the "Suspended" state. Then you need to contact support. Support might restore your managed domain, but only if a backup that is less than 30 days old exists.
The managed domain only stays in a suspended state for 15 days. To recover your managed domain, Microsoft recommends that you resolve critical alerts immediately.
We have a 'Basic' support plan and there were absolutely no change made in Azure portal. So in order for us to have this investigated by Azure support, we have to buy a Support Plan? For something that we didn't break?
Thank you all for your help,
Karim.
Hello,
I had to reinstall Azure AD Connect after server formatting and I get the following error, using Custom settings:
[ERROR] A terminating unhandled exception occurred.Do you have any idea about the origin of the problem?
Thank you.
Bertrand
Dear Microsoft,
I have noticed in our Azure Information Protection (AIP) tenant that we have preview access to the new reporting and dashboard. I have configured the reports to use Log Analytics (OMS dashboard) but each time I access the report I get a message saying that log analytics needs configuring.
Can anyone point me at the preview documentation or have any suggestions.
Kind Regards
Luke.
Hey,
We tried to use Azure Ad join with some of our laptops.
Everything goes fine with connecting, and the laptop registers in azure.
But after rebooting the laptop the device gets stuck in a never ending circle, crashes ( the boot circle of dots)
As far as i'm aware there is still no solution for this?
Or can anyone help?
Edited:
Seems like it happends when changing Workgroup?
After joining Windows 10 devices to Azure AD, the subsequent reboot shows spinning wheel and the loading never ends. The devices are unusable then.
If we turn off ELAM (Early Launch Antimalware) driver in boot menu, the devices will utimately finish booting after some cca 3 hours of waiting, every time.
Steps tried to survive AAD join:
- latest everything. latest Windows (1709) with all updates (as for 28th Feb 2018) installed
- difference in EMS or Intune. Joined via account with Intune licence (EMS E3, but with no policies set) or joined via account with just AAD Premium P2 (so just EMS policies, no Intune) made no difference
- integrity scan. sfc /scannow before and after join (when it booted with disabled ELAM) made no difference
- device name uniquiness. renaming the device to definitely unique computername and restart, before join
But no luck.
This is happening to us with hyperv guests but also with physical laptops we have tried, both Lenovo and Dell.
What we can try next:
1) we are using custom image of Win10 version 1709 with various software installed and policies set. No antivirus there. We will try step by step new image creation process to see which might have an effect
2) install our image to UEFI instead on BIOS partition. This try came from idea that turning of ELAM partially helps for booting
Any ideas anyone?
Keywords: spinning wheel, aad join, stucked, bricked, problem
I followed a tutorial here and working fine when running in local:
https://docs.microsoft.com/en-us/azure/active-directory/develop/GuidedSetups/active-directory-aspnetwebapp-v1#configure-your-webconfig-and-register-an-application
When I transfer it in our server, I encountered this error.
Though it is showing that the password is successfully changed, it is not allowing me to login with the new password and it is still accepting old password only. Can someone help me on this
Thanks
Hello,
Is it possible to authenticate users who are accessing their Tenants Azure Portal against a 3rd part SAML 2.0 IdP. This can be SP initiated or IdP initiated. Either or would work. If this is possible, could someone point me in the right direction for documentation for configuring this.
I have found the following which seems to be along the lines of what I'm trying to accomplish, but I am not sure if this is applicable to the actual Azure Management Portal.
https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-fed-saml-idp
Thanks!
Hello,
we are planning to sync two different AD forests to O365 with one Azure AD Connect Server.
The Forests have same:
Forest A: corp.local
Forest B: corp.local
Will this be a problem? Is there a workarround for this enviroment?
Thanks.