Update use-prediction-api.md with explicit requirement to view API Keys #106
Conversation
I was giving a user all of the "Cognitive Services Custom Vision" roles and he could create the models, but he could not view the Prediction Key. It was frustrating that this documentation did not explain the role needed to view the key.
|
@ramseyjacob : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit c7d5034:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/ai-services/custom-vision-service/use-prediction-api.md | Details |
articles/ai-services/custom-vision-service/use-prediction-api.md
- Line 44, Column 37: [Warning: hard-coded-locale - See documentation]
Link 'https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/ai-machine-learning#cognitive-services-user' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 44, Column 37: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/ai-machine-learning#cognitive-services-user' will be broken in isolated environments. Replace with a relative link.
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:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
|
@PatrickFarley Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
I was giving a user all of the "Cognitive Services Custom Vision" roles and he could create the models, but he could not view the Prediction Key. It was frustrating that this documentation did not explain the role needed to view the key.