Frequently Asked Questions
General Questions
What is Azure2Git?
Azure2Git is a service that automatically captures and stores hourly snapshots of your Azure environment configuration in Git repositories.
How often are snapshots taken?
Snapshots are taken hourly by default. This interval ensures you have up-to-date documentation while managing storage efficiently.
Which environments can be scanned?
- Azure Resource configurations
- Entra ID (formerly Azure AD) settings
- Intune configurations
Technical Questions
What permissions are required?
- For Azure: Contributor role on scanned resources
- For Entra ID/Intune: Application Administrator
- For Azure DevOps: Project Collection Administrator
How secure is the solution?
Azure2Git uses managed identities and doesn't store any credentials. All access is handled through Azure's native security mechanisms.
Can I customize the scanning interval?
Currently, the scanning interval is fixed at hourly intervals to balance documentation freshness with system performance.
Where is the data stored?
All configuration data is stored in your own Azure DevOps Git repositories, giving you full control over the data.
Operational Questions
How do I monitor the service?
You can monitor the service through: 1. The Azure2Git web interface 2. Azure Application Insights 3. Azure Portal metrics
What happens if a scan fails?
Failed scans are automatically retried. You can view scan status in the web interface and configure alerts for repeated failures.
How much storage is needed?
Storage requirements depend on your environment size. Typically, a medium-sized environment requires 1-2 GB per year of history.
Support
How do I get help?
- Check this documentation
- Contact support at support@just-software.com
- Open a support ticket through Azure Portal
Is there a limit to API calls?
Azure2Git respects Azure API throttling limits and automatically manages request rates to prevent disruption.