This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 26%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESR%3C/text%3E%3C/svg%3E)
I have migrated Application insights to workspace based.
There is multiple resources of a resource group and upon migrating it created same workspace name for all resources, however workspace Id is different for all resources.
Wanted to know how can we give different workspace name to each resources.
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 39%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
@Sanskriti Rathore Kindly note that the renaming of log analytics workspace is not supported as of now. If you haven't done much post-setup configuration, you can create a new workspace and link it to application insights.
Hello,
Can you let me know what is post-setup configuration.
@Sanskriti Rathore After the migration is done, you may configure the workspace's daily cap to limit ingestion and costs instead of the cap in Application Insights. Also, the telemetry records also take up to sometime to show up in log analytics workspace linked to application insights. There are things I called as post-setup configuration.
@Sanskriti Rathore After the migration is done, you may configure the workspace's daily cap to limit ingestion and costs instead of the cap in Application Insights. Also, the telemetry records also take up to sometime to show up in log analytics workspace linked to application insights. There are things I called as post-setup configuration.
I also need some additional information post migration.
It would be a great help if you can answer above questions.
After you migrate your Application Insights resource to a workspace-based resource, you can verify the migration by checking the corresponding workspace information in the Overview pane. You can access the Overview pane by selecting your workspace-based Application Insights resource in the Azure portal. If the migration is successful, you should see the workspace name in the Overview pane.
To test if the workspace-based resource is working fine, you can create and run queries in the Log Analytics workspace associated with your workspace-based Application Insights resource. You can also create and test alerts and dashboards in the Log Analytics workspace. Kindly note when you query directly from the Log Analytics workspace, you only see data that's ingested post migration. To see both your classic Application Insights data and the new data ingested after migration in a unified query experience, use the Logs tab from within your migrated Application Insights resource.
To verify the impact of the migration from Application Insights to workspace-based, you can compare the usage and costs of your classic Application Insights resource with the usage and costs of your workspace-based Application Insights resource. You can view the usage and costs of your workspace-based Application Insights resource in the Azure portal. You can also use the workspace's daily cap to limit ingestion and costs instead of the cap in Application Insights
Reference document:
https://learn.microsoft.com/en-us/azure/azure-monitor/app/convert-classic-resource