Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Infobric Equipment to user provisioning documentation #1360

Open
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

CvBlixen
Copy link

Infobric Equipment is a system for keeping track of Equipment, and this is how to set up Entra user provisioning for our system. 🙂

@CvBlixen
Copy link
Author

@microsoft-github-policy-service agree company="Infobric AB"

Copy link
Contributor

Learn Build status updates of commit 93ae24a:

⚠️ Validation status: warnings

File Status Preview URL Details
docs/identity/saas-apps/infobric-equipment-provisioning-tutorial.md ⚠️Warning Details
docs/identity/saas-apps/media/infobric-equipment-provisioning-tutorial/connect-your-application.png ✅Succeeded
docs/identity/saas-apps/media/infobric-equipment-provisioning-tutorial/enable-entra-provisioning.png ✅Succeeded
docs/identity/saas-apps/media/infobric-equipment-provisioning-tutorial/endpoint-and-token-pasted-to-entra.png ✅Succeeded
docs/identity/saas-apps/media/infobric-equipment-provisioning-tutorial/entry-sync-notifications-recipient.png ✅Succeeded
docs/identity/saas-apps/media/infobric-equipment-provisioning-tutorial/manage-entra-groups-button.png ✅Succeeded
docs/identity/saas-apps/media/infobric-equipment-provisioning-tutorial/manage-entra-groups.png ✅Succeeded
docs/identity/saas-apps/media/infobric-equipment-provisioning-tutorial/pick-company.png ✅Succeeded
docs/identity/saas-apps/media/infobric-equipment-provisioning-tutorial/provion-user-on-demand-success.png ✅Succeeded
docs/identity/saas-apps/media/infobric-equipment-provisioning-tutorial/single-user-added-to-application.png ✅Succeeded
docs/identity/saas-apps/media/infobric-equipment-provisioning-tutorial/start-provisioning.png ✅Succeeded
docs/identity/saas-apps/media/infobric-equipment-provisioning-tutorial/successful-connection-test.png ✅Succeeded
docs/identity/saas-apps/toc.yml ✅Succeeded

docs/identity/saas-apps/infobric-equipment-provisioning-tutorial.md

  • Line 22, Column 100: [Warning: file-not-found - See documentation] Invalid file link: '~/identity/application-provisioning/user-provisioning.md'.
  • Line 12, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'CvBlixen' is not a valid Microsoft alias.
  • Line 152, Column 4: [Suggestion: duplicate-alt-text - See documentation] Alt text 'Screenshot of Start provisioning.' is duplicated. Within an article, alt text must be unique.
  • Line 163, Column 4: [Suggestion: duplicate-alt-text - See documentation] Alt text 'Screenshot of Start provisioning.' is duplicated. Within an article, alt text must be unique.
  • Line 167, Column 4: [Suggestion: duplicate-alt-text - See documentation] Alt text 'Screenshot of Start provisioning.' is duplicated. Within an article, alt text must be unique.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

@ttorble
Copy link
Contributor

ttorble commented Feb 14, 2025

@jeevansd

Can you review the proposed changes? I've emailed you with further details about working with new content submissions in the public repo. Thanks.

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants