OfficeDev / microsoft-teams-apps-company-communicator

Company Communicator app template
MIT License
327 stars 400 forks source link

Unable to add a TXT record to the domain DNS for the validation in Front Door and CDN profile #1544

Open NikhilDhumal734 opened 3 weeks ago

NikhilDhumal734 commented 3 weeks ago

We followed the steps from Microsoft article : https://techcommunity.microsoft.com/t5/modern-work-app-consult-blog/migrating-company-communicator-between-azure-subscriptions/ba-p/3646546

But After creating Azure Front Door and CDN profiles manually we are getting message as The domain should be validated for traffic delivery. You should add a TXT record to the domain DNS for the validation.

As we unable to add a TXT record to the domain DNS for the validation. image

Looking forward for your help

tiwariShiv7 commented 3 weeks ago

Hi @NikhilDhumal734 , Thanks for reaching out to us. We will be able to respond upon this following an internal discussion. We will get back to you within 48 Hours.

tiwariShiv7 commented 3 weeks ago

Hi @NikhilDhumal734 , Azure Front Door and CDN profiles gets created automatically with official version deployment. I think we are following custom deployment here and I am afraid according to our support scope this is out of scope

NikhilDhumal734 commented 3 weeks ago

Hi @tiwariShiv7

To update, we copied all the existing company communicator resource files from one resource group to another as we need to change the subscription, we followed the below article for Front-door migration Link : https://learn.microsoft.com/en-us/azure/frontdoor/migrate-tier

As we unable to copy existing Front door and CDN profile so we created manually and after we are getting message as The domain should be validated for traffic delivery. You should add a TXT record to the domain DNS for the validation.

Unfortunately, our network admin team also has no control/scope to add a txt record to Domain Name System. Please help to assist us further on this case.

v-jaygupta commented 2 weeks ago

Hello @NikhilDhumal734 ,

We have analyzed the request for FrontDoor migration from one subscription to another and concluded that there are a significant number of dependencies associated with the Front Door resource during the transfer. We would strongly recommend proceeding with a fresh deployment, using our official repository as the primary source.

peddivyshnavi commented 1 week ago

@NikhilDhumal734 Could you please update us on the status of the issue?

peddivyshnavi commented 5 days ago

@NikhilDhumal734 Could you please update us on the status of the issue?

peddivyshnavi commented 1 day ago

@NikhilDhumal734 Please let us know if you are still facing this issue and require assistance and we will be happy to discuss. If no further action is needed at the moment and no response is received, we will close out the issue in 2 business days.