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

Paragraph Credentials #5048

Closed
Werner-MOC opened this issue Feb 27, 2018 — with docs.microsoft.com · 4 comments
Closed

Paragraph Credentials #5048

Werner-MOC opened this issue Feb 27, 2018 — with docs.microsoft.com · 4 comments

Comments

Copy link

As the storage location for Backups should allways be outside of Azure Stack, it does not make any sense to use Credentials from Azure Stack Administrator. Bad and missleading example: for example, you may use the Azure Stack administrator credentials.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

  • ID: a868d70f-4b98-7a38-5aea-f42f37ec4524
  • Version Independent ID: e27eb785-922f-55ca-4b12-ca978e5e8680
  • Content
  • Content Source
  • Service: azure-stack
@amanarneja
Copy link
Contributor

Thanx for pointing this out! I have assigned the issue to the author to investigate and update.

@ghost ghost added the azure-stack/svc label Feb 27, 2018
@mattbriggs
Copy link
Contributor

Thank you for your feedback. I can see how that would seem misleading. In order to use the Instrastructure Backup Service, you need "a domain user account and credentials, for example, you may use the Azure Stack administrator credentials." This service is running on Azure Stack. Your target location for the backups, you are right, should ideally be in a physically removed location. However, not every single instance of Azure Stack has access to remote physical locations.

@Werner-MOC
Copy link
Author

Werner-MOC commented Feb 28, 2018 via email

@mattbriggs
Copy link
Contributor

#please-close

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

No branches or pull requests

4 participants