- If this server needs a static MAC address, Azure cannot support this at this time. We will be unable to migrate your server to Azure.
- When selecting a date to migrate your server, keep in mind this service request will take around 4 weeks to complete. Please select a date to migrate far enough in the future to work through this service request.
-
Access Changes: After migration, you may notice changes in how you connect to your server. AVD uses a different access method than what you're used to. Some users may need to adjust how they connect.
-
Security Enhancements: We are aligning with the latest security standards. Because of this, some existing broad access rules on campus will be refined, which could affect connectivity for certain users.
-
External Connections: If your server needs to reach public IP addresses on campus, there may be routing limitations. If a route doesn’t currently exist, we’ll work with the Information Security team to explore secure solutions. This might impact the timeline of your migration.
-
What Stays the Same (and What Doesn’t): This migration is a “lift and shift.” Your server will move to Azure exactly as it is now—same settings, same configuration.
-
If you want your server reset to factory defaults, please let us know before the migration so we can coordinate with our Enterprise Systems team.
-
If you're looking to change how the server functions or behaves post-migration, we’re happy to support that as a separate project after the move. Custom changes are not part of this initial migration scope.