Updating the existing Cosgrid Networks application documentation in the Microsoft Entra application gallery

Priya Darshini 0 Reputation points
2026-10-26T10:23:23.5966667+00:00

Hi Team,

I need clarification regarding the correct process for updating the existing Cosgrid Networks application documentation in the Microsoft Entra application gallery.

What we did previously

Around five months ago, we submitted a pull request (#2076) to the public MicrosoftDocs/entra-docs GitHub repository to update the existing Cosgrid Networks SAML tutorial and add documentation for OIDC and SCIM provisioning.

During the review, [Moderator note: Personally Identifiable Information removed] advised us that Microsoft authors should make these content changes through the private repository so that the documentation could be staged and validated correctly. We were asked to move the changes to the private repository and resolve the validation issues. Following this guidance, our public pull request was closed.

What we are trying to do now

We want to update the documentation for our existing Cosgrid Networks application. We are not trying to create a new application gallery listing.

While investigating the correct process, we encountered an access issue when opening the Microsoft Application Network (MAN) portal. Our external ISV account ([Moderator note: Personally Identifiable Information removed]@cosgrid.com) receives an AADSTS50020 error stating that the account does not exist in the Microsoft tenant.

What we found in Microsoft Learn Q&A

We raised a question on Microsoft Learn Q&A to understand the correct procedure. A community responder explained that SaaS application tutorials are maintained in the public MicrosoftDocs/entra-docs repository and that documentation updates are generally made by editing the tutorial through its GitHub Edit link and submitting a pull request.

The responder also explained that the MAN portal is primarily used to manage application gallery listings, including SSO, provisioning, MDM, and application removal. They could not find official documentation confirming that MAN access is required for documentation-only updates.

This guidance appears to differ from the instructions we received during the review of our earlier pull request.

Clarification needed

Could you please confirm the following?

Should we submit a new pull request to the public MicrosoftDocs/entra-docs repository, or must we make the changes through a private Microsoft documentation repository?

If the private repository is required, could you provide its name and explain how an external ISV contributor can obtain the necessary access?

Is access to the Microsoft Application Network portal required to update the documentation for an existing application, or is it needed only when changing the gallery listing itself?

Why was our previous pull request directed to the private repository and closed, while the general guidance on Microsoft Learn Q&A suggests using the public GitHub repository?

Could you please confirm the recommended workflow for external ISVs who need to update the documentation for an existing Microsoft Entra gallery application?

We want to follow the correct Microsoft process and avoid submitting another pull request through an unsupported workflow.

Thank you for your guidance.

Best regards,[Moderator note: Personally Identifiable Information removed]

Microsoft Teams | Development
Microsoft Teams | Development

Building, integrating, or customizing apps and workflows within Microsoft Teams using developer tools and APIs

0 comments

2 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Jayden-P 4,225 Reputation points Independent Advisor
    2026-10-26T11:37:12.31+00:00

    Please note that this forum is not Microsoft support, this is a user-to-user support forum.

    Hi @Priya Darshini

    I would recommend referring to the AI answer, as it contains several useful observations and aligns with the publicly available guidance regarding Microsoft Entra App Gallery updates. In particular, the recommendation to engage the App Gallery publishing team appears reasonable given that your request involves not only documentation updates, but also the addition of new capabilities such as OIDC and SCIM provisioning.

    That said, the response was provided by a forum contributor and relies on publicly available information. Since your situation involves a previous pull request (#2076) that was specifically reviewed by Microsoft and redirected to a private workflow, it may not fully reflect the internal process that was communicated to your organization at that time.

    If you require an official Microsoft response or further investigation into the previous guidance, please consider opening a support ticket with Microsoft so the appropriate App Gallery or documentation team can review the details of your case and provide definitive guidance.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-10-26T10:25:46.7866667+00:00

    The AADSTS50020 block has no documented tenant-side fix for Cosgrid; request Microsoft to grant access or provide an alternate intake route for the existing Cosgrid listing before submitting another public documentation pull request.

    Your proposed work combines two different change types:

    • Corrections to the existing published SAML article can normally be proposed through the article’s Edit link and a public GitHub pull request.
    • Adding OIDC and SCIM capabilities changes the supported Gallery integration and customer setup experience. That requires Gallery validation and the existing-application update process; a documentation PR alone is insufficient. Microsoft requires validation for each capability being published, and material integration changes must be validated again.^1^

    Proceed as follows:

    1. Contact the App Gallery publishing team through the Microsoft Entra App Gallery Self-Service Publishing Feedback form. The publishing documentation identifies that form as the support route for publishing problems.^1^
    2. Include:
      • Application name: Cosgrid Networks
      • Existing Gallery listing and tutorial
      • The previous PR number: #2076
      • The exact AADSTS50020 message, timestamp, and a redacted screenshot
      • The account domain and home tenant, without credentials or secrets
      • The requested changes: SAML tutorial revision, OIDC addition, and SCIM addition
      • Any existing Submission ID or Test IDs
      • A request for case-by-case handling of an existing application update
      • A request to confirm whether Microsoft will grant MAN access, create an update submission, or assign a Microsoft author to stage the content privately
    3. Do not create a duplicate Gallery submission. Microsoft explicitly directs publishers of existing applications to the existing-application update process.^1^
    4. Wait for the Gallery/content team to identify the correct repository and staging route before recreating the combined PR.

    MAN portal access

    The official existing-application procedure still says to use the Microsoft Application Network portal:

    1. If a Request Access page appears, submit the business justification.
    2. After access is granted, select Submit Request (ISV).
    3. Select Update my application's listing in the gallery.
    4. Choose the applicable SSO update option.^2^

    For SCIM, the documented menu option is Improve my application's User Provisioning feature, but that wording applies to an existing provisioning integration.^2^ Because Cosgrid is adding SCIM for the first time, ask the Gallery team to confirm the intake route rather than selecting that option without instruction.

    Your account does not reach the Request Access page. A Microsoft Q&A response reports that external MAN access can be restricted and that roles, guest configuration, or permissions in the ISV tenant cannot bypass that restriction.^3^ That case concerned a new submission, so it does not conclusively define how every existing-app update is handled. It does establish that repeatedly changing Cosgrid tenant permissions is not a supported solution to the reported portal restriction.

    Public versus private repository

    Microsoft’s general contribution model allows edits to publicly hosted Learn documentation:

    • For a single-article revision, select Edit on the article and open a PR.
    • For larger or multi-article work, fork and clone the public repository, make the changes locally, and open a PR.^4^

    The Cosgrid PR publicly confirms that the proposed change combined SAML, OIDC, and SCIM content and that it was closed.^5^ The accessible record does not establish the internal validation issue or why a private repository was required. Your reported reviewer instruction is therefore the controlling direction for that specific submission, but it does not mean external ISVs generally receive private-repository access.

    The likely operational outcome is that a Microsoft content owner stages capability-related content in the private authoring environment after Gallery validation. No public documentation identifies the private repository or an external access-request procedure, so its name or access method should not be guessed.

    If Microsoft confirms that only corrections to the already-published SAML article remain, use the article’s Edit link and submit a narrowly scoped public PR. Do not include new OIDC or SCIM integration claims in that PR unless the Gallery team confirms those capabilities have completed validation and authorizes that contribution route.

    References

    1. Publish your app to Microsoft Entra App Gallery
    2. Update or remove your app from the Microsoft Entra App Gallery
    3. Unable to access the Microsoft Application Network Portal (errorCode: AADSTS50020) - Microsoft Q&A
    4. Overview of editing documentation on Microsoft Learn
    5. #2076 Update Cosgrid Networks SAML tutorial; add OIDC and SCIM provisioning…
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.