Share via

Parental Consent Loop: "This account cannot give parental consent" error when adding child

Chammi Kumara 0 Reputation points
2026-02-09T09:16:25.55+00:00

Same symptoms as explained in the question below

https://learn.microsoft.com/en-us/answers/questions/5675146/parental-consent-loop-this-account-cannot-give-par

Opened a support ticket [Moderation note: PII removed] where the support engineer suggested I ask the question again here. I have a technical loop and now seems to have a support loop as well. Can someone please help?

Microsoft 365 and Office | Microsoft Family Safety | For home | Windows
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Kai-H 12,220 Reputation points Microsoft External Staff Moderator
    2026-02-11T09:55:23.28+00:00

    Hi, Chammi Kumara

    Thanks for reaching out to Microsoft Q&A forum.

    Please note that our forum is a public platform, and we will modify your question to hide your personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data. 

    Sorry for this frustrating experience that you're encountering. This loop usually means Microsoft has the child-consent “authority record” tied to a different adult account (or the child account’s compliance status is out of sync), so the consent portal rejects your Organizer sign-in even though your family role looks correct.

    Here are some suggestions you can try:

    Use the dedicated consent management page (not the in-flow prompt)

    Go straight to Microsoft’s consent management experience and try completing consent there, ideally from a desktop browser: the “Manage consent” flow is designed specifically for statutory-age approvals and is often more reliable than device prompts. This matters because Family Safety roles and parental-consent authority are related but not identical.

    Confirm you are using the same adult account that originally granted consent

    Even if you are the current Organizer, Microsoft only lets the adult who originally granted consent manage or re-grant that consent. If you have ever used another personal Microsoft account in the past, sign in with those as well and check whether the child appears under consent management. This works because the backend permission can be anchored to the “original consenting adult,” not the current Organizer.

    Refresh the child’s family linkage (remove and re-add)

    From the family portal, remove the child member and add them back, then retry consent from the web. This can rebuild the association between the child account and the family group when the invite acceptance succeeded but the consent binding did not.

    If age/region status recently changed, move the child to a new family group and re-consent

    In some “statutory age” edge cases, Microsoft’s mitigation is to migrate the account into another family group as a child and have an Organizer provide consent again. This helps when the account’s age classification and family permissions conflict on the backend.

    Hope this helps. Feel free to get back if you have other questions.

    Since this is a public forum, we will hide your personal identifiable information, and I have sent that image of yours containing your personal identifiable information in a private message so we can work together to resolve the issue. Also, please check your private message in case you want to share another screenshot to avoid leaking your PII by click on the Private Message button as show below.

    User's image


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment."    

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.