You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/service-limits.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -291,6 +291,19 @@ The following timeouts apply to the Azure Communication Services Calling SDKs:
291
291
| PSTN call establishment timeout. | 115 |
292
292
| Promote a 1:1 call to a group call timeout. | 115 |
293
293
294
+
### Virtual Rooms
295
+
The throttling policies of rooms service are determined by grouping requests through **resource id**.
296
+
297
+
| API | Threshold |
298
+
|--|--|
299
+
| Create Room | 20 req/sec |
300
+
| Update Room | 20 req/sec |
301
+
| Delete Room | 20 req/sec |
302
+
| Get Room | 40 req/sec |
303
+
| List Rooms | 10 req/sec |
304
+
| Update participant | 20 req/sec |
305
+
| List participants | 40 req/sec |
306
+
294
307
### Action to take
295
308
296
309
For more information about the voice and video calling SDK and service, see [Calling SDK overview](./voice-video-calling/calling-sdk-features.md) or [Known issues in the SDKs and APIs](./known-issues.md). You can also submit a request to [Azure Support](/azure/azure-portal/supportability/how-to-create-azure-support-request) to increase some of the limits. Our vetting team reviews all requests.
Copy file name to clipboardExpand all lines: articles/container-apps/tutorial-java-quarkus-connect-managed-identity-postgresql-database.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ What you learn:
21
21
22
22
> [!div class="checklist"]
23
23
> * Configure a Quarkus app to authenticate using Microsoft Entra ID with a PostgreSQL Database.
24
-
> * Create an Azure container registry and push a Java app image to it.
24
+
> * Create an Azure Container Registry instance and push a Java app image to it.
25
25
> * Create a Container App in Azure.
26
26
> * Create a PostgreSQL database in Azure.
27
27
> * Connect to a PostgreSQL Database with managed identity using Service Connector.
@@ -49,7 +49,7 @@ LOCATION="eastus"
49
49
az group create --name $RESOURCE_GROUP --location $LOCATION
50
50
```
51
51
52
-
Create an Azure container registry instance using the [az acr create](/cli/azure/acr#az-acr-create) command and retrieve its login server using the [az acr show](/cli/azure/acr#az-acr-show) command. The registry name must be unique within Azure and contain 5-50 alphanumeric characters. All letters must be specified in lower case. In the following example, `mycontainerregistry007` is used. Update this to a unique value.
52
+
Create an Azure Container Registry instance using the [az acr create](/cli/azure/acr#az-acr-create) command and retrieve its login server using the [az acr show](/cli/azure/acr#az-acr-show) command. The registry name must be unique within Azure and contain 5-50 alphanumeric characters. All letters must be specified in lower case. In the following example, `mycontainerregistry007` is used. Update this to a unique value.
Copy file name to clipboardExpand all lines: articles/iot-central/core/howto-transform-data.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,7 +108,7 @@ In this scenario, the IoT Edge device runs a custom module that transforms the d
108
108
- Build the custom module.
109
109
- Add the custom module to a container registry.
110
110
111
-
The IoT Edge runtime downloads custom modules from a container registry such as an Azure container registry or Docker Hub. The [Azure Cloud Shell](../../cloud-shell/overview.md) has all the tools you need to create a container registry, build the module, and upload the module to the registry:
111
+
The IoT Edge runtime downloads custom modules from a container registry such as an Azure Container Registry or Docker Hub. The [Azure Cloud Shell](../../cloud-shell/overview.md) has all the tools you need to create a container registry, build the module, and upload the module to the registry:
Copy file name to clipboardExpand all lines: articles/migrate/appcat/java-preview.md
+75-52Lines changed: 75 additions & 52 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,8 +28,8 @@ The tool is designed to help organizations modernize their Java applications in
28
28
29
29
With it, you can perform the following tasks:
30
30
31
-
* Discover technology usage: Quickly see which technologies an application uses. Discovery is useful if you have legacy applications with not much documentation and want to know which technologies they use.
32
-
* Assess the code to a specific target: Assess an application for a specific Azure target. Check the effort and the modifications you have to do to replatform your applications to Azure.
31
+
- Discover technology usage: Quickly see which technologies an application uses. Discovery is useful if you have legacy applications with not much documentation and want to know which technologies they use.
32
+
- Assess the code to a specific target: Assess an application for a specific Azure target. Check the effort and the modifications you have to do to replatform your applications to Azure.
33
33
34
34
### Supported targets
35
35
@@ -50,13 +50,13 @@ The rules used by Azure Migrate application and code assessment are grouped base
50
50
51
51
When the tool assesses for Cloud Readiness and related Azure services, it can also report useful information for potential usage of different Azure services. The following list shows a few of the services covered:
52
52
53
-
* Azure Databases
54
-
* Azure Service Bus
55
-
* Azure Storage
56
-
* Azure Content Delivery Network
57
-
* Azure Event Hubs
58
-
* Azure Key Vault
59
-
* Azure Front Door
53
+
- Azure Databases
54
+
- Azure Service Bus
55
+
- Azure Storage
56
+
- Azure Content Delivery Network
57
+
- Azure Event Hubs
58
+
- Azure Key Vault
59
+
- Azure Front Door
60
60
61
61
## Download and Install
62
62
@@ -75,30 +75,29 @@ For the JDK requirement, we recommend you use the [Microsoft Build of OpenJDK](/
75
75
| macOS | Apple Silicon |[Download][10]|[sha256][11] / [sig][12]|
76
76
| Linux | AArch64 / ARM64 |[Download][4]|[sha256][5] / [sig][6]|
-[Download](/java/openjdk/download#openjdk-17) and [install Microsoft Build of OpenJDK 17](/java/openjdk/install). Ensure that the **JAVA_HOME** environment variable is set.
100
100
-[Download Apache Maven](https://maven.apache.org/download.cgi) and [install locally](https://maven.apache.org/install.html). Ensure that the Maven binary (`mvn`) is reachable through `PATH` environment variable.
101
-
-[Download and install Python 3](https://www.python.org/downloads/).
102
101
103
102
### Installation
104
103
@@ -116,26 +115,14 @@ Extract the binary from the downloaded file. You should see the following folder
116
115
├── maven.default.index
117
116
├── jdtls/
118
117
├── static-report/
119
-
├── rulesets/
118
+
├── rulesets/
120
119
├── readme.md
121
120
└── readme.html
122
121
```
123
122
124
123
### Running the tool
125
124
126
-
#### Option 1: Run appcat from the downloaded folder
127
-
128
-
Change the directory to the extracted folder:
129
-
130
-
```bash
131
-
cd /azure-migrate-appcat-for-java-cli-<OS>-<architecture>-<release-version>-preview/
132
-
./appcat --help
133
-
```
134
-
135
-
> [!NOTE]
136
-
> The `appcat` binary first looks for its dependencies in the current directory, where it's running from, and falls back to the following scenario if they aren't found.
137
-
138
-
#### Option 2: Add the appcat binary path to your $PATH
125
+
#### Option 1: Add the appcat binary path to your $PATH
139
126
140
127
Move the contents of the folder to the **.appcat** folder in the user's home directory - **$HOME/.appcat** on Linux/Mac and **%USERPROFILE%/.appcat** on Windows.
> In this context, when the `appcat` binary is called from a different folder than where it's installed, it looks for its dependencies in the **.appcat** folder in the user's home directory.
146
+
> When the `appcat` binary is called from a different folder than where it's installed, it looks for its dependencies in the **.appcat** folder in the user's home directory.
147
+
148
+
#### Option 2: Run appcat from the downloaded folder
149
+
150
+
Change the directory to the extracted folder:
151
+
152
+
```bash
153
+
cd /azure-migrate-appcat-for-java-cli-<OS>-<architecture>-<release-version>-preview/
154
+
./appcat --help
155
+
```
156
+
157
+
> [!NOTE]
158
+
> The `appcat` binary first looks for its dependencies in the current directory. If the dependencies aren't found, it falls back to the configuration described in the [Option 1](#option-1-add-the-appcat-binary-path-to-your-path) section.
160
159
161
160
## Usage
162
161
@@ -173,7 +172,7 @@ AppCAT provides two subcommands for usage:
@@ -241,7 +240,6 @@ available target technologies:
241
240
azure-aks
242
241
azure-appservice
243
242
azure-container-apps
244
-
azure-spring-apps
245
243
cloud-readiness
246
244
linux
247
245
openjdk11
@@ -332,34 +330,52 @@ The reports are automatically generated and launched. You can find the reports u
332
330
333
331
The landing page of the report lists all the technologies that are used in the application. The dashboard provides a summary of the analysis, including the number of transformation incidents, the incidents categories, or the story points.
334
332
335
-
:::image type="content" source="media/java/report-summary.png" alt-text="Screenshot of the appcat summary report." lightbox="media/java/report-summary.png":::
333
+
:::image type="content" source="media/java/appcat-7-report-summary.png" alt-text="Screenshot of the appcat summary report." lightbox="media/java/appcat-7-report-summary.png":::
336
334
337
335
When you zoom in on the **Incidents by Category** pie chart, you can see the number of incidents by category: **Mandatory**, **Optional**, and **Potential**.
338
336
339
337
The dashboard also shows the *story points*. The story points are an abstract metric commonly used in Agile software development to estimate the level of effort needed to implement a feature or change. `appcat` uses story points to express the level of effort needed to migrate a particular application. Story points don't necessarily translate to work hours, but the value should be consistent across tasks.
340
338
341
-
:::image type="content" source="media/java/report-summary-incident.png" alt-text="Screenshot of the AppCAT summary incident report." lightbox="media/java/report-summary-incident.png":::
339
+
:::image type="content" source="media/java/appcat-7-report-summary-incident.png" alt-text="Screenshot of the AppCAT summary incident report." lightbox="media/java/appcat-7-report-summary-incident.png":::
342
340
343
341
### Assessment report
344
342
345
343
The assessment report gives an overview of the transformation issues that would need to be solved to migrate the application to Azure.
346
344
347
345
These *Issues*, also called *Incidents*, have a severity (*Mandatory*, *Optional*, or *Potential*), a level of effort, and a number indicating the story points. The story points are determined by calculating the number of incidents times the effort required to address the issue.
348
346
349
-
:::image type="content" source="media/java/report-assessment.png" alt-text="Screenshot of the AppCAT assessment report." lightbox="media/java/report-assessment.png":::
347
+
:::image type="content" source="media/java/appcat-7-report-assessment.png" alt-text="Screenshot of the AppCAT assessment report." lightbox="media/java/appcat-7-report-assessment.png":::
350
348
351
349
### Detailed information for a specific issue
352
350
353
351
For each incident, you can get more information (the issue detail, the content of the rule, and so on) just by selecting it. You also get the list of all the files affected by this incident.
354
352
355
-
:::image type="content" source="media/java/report-assessment-detail.png" alt-text="Screenshot of the AppCAT issue detail report." lightbox="media/java/report-assessment-detail.png":::
353
+
:::image type="content" source="media/java/appcat-7-report-assessment-detail.png" alt-text="Screenshot of the AppCAT issue detail report." lightbox="media/java/appcat-7-report-assessment-detail.png":::
356
354
357
355
Then, for each file or class affected by the incident, you can jump into the source code to highlight the line of code that created the issue.
358
356
359
-
:::image type="content" source="media/java/report-assessment-code.png" alt-text="Screenshot of the AppCAT issue code report." lightbox="media/java/report-assessment-code.png":::
357
+
:::image type="content" source="media/java/appcat-7-report-assessment-code.png" alt-text="Screenshot of the AppCAT issue code report." lightbox="media/java/appcat-7-report-assessment-code.png":::
360
358
361
359
## Release notes
362
360
361
+
### 7.6.0.4
362
+
363
+
This release contains the following fixes and enhancements.
364
+
365
+
- Supports telemetry collection. Use the `--disable-telemetry` flag to disable telemetry.
366
+
- Refactors the CLI command format to make it more clear.
367
+
- Updates the `--source` flag, changing from `--source <source1> --source <source2> ...` to `--source <source1>,<source2>,...`
368
+
- Updates the `--target` flag, changing from `--target <target1> --target <target2> ...` to ` --target <target1>,<target2>,...`
369
+
- Updates the `--rules` flag, changing from `--rules <rule1> --rules <rule2> ...` to `--rules <rule1>,<rule2>,...`
370
+
- Updates the `--maven-settings` flag to `--custom-maven-settings`
371
+
- Updates the `--limit-code-snips` flag to `--code-snips-number`
372
+
- Removes the `--json-output` flag, use `--output-format` flag, choose output format: 'yaml' or 'json'. (default yaml)
373
+
- Removes the `--provider`, `--override-provider-settings`, `--list-providers`, and `--dependency-folders` flags
374
+
- A new `--exclude-paths` flag: Specifies paths that should be ignored in analysis. Use a comma-separated list for multiple values: `--exclude-paths <path1>,<path2>,...`. The default value is `[]`.
375
+
- A new `--packages` flag: Specifies application class packages to be evaluated. Use a comma-separated list for multiple values: `--packages <package1>,<package2>,...`. The default value is `[]`.
376
+
- A new `--dry-run` flag: Only checks whether the flags are valid without actually running the analysis actually. The default value is `false`.
377
+
- Removes `azure-spring-apps` from the appcat `--list-targets`.
378
+
363
379
### 7.6.0.3
364
380
365
381
This release contains the following fixes and enhancements.
@@ -438,6 +454,13 @@ GA (Generally Available) release of Azure Migrate application and code assessmen
438
454
439
455
## Known Issues
440
456
457
+
### 7.6.0.4
458
+
459
+
- Rules issues:
460
+
- The `azure-system-config-01000` rules aren't being triggered.
461
+
- The `azure-password-01000` rule detects only one violation, even when multiple violations exist in the same file.
462
+
- An error in the Watcher Error channel on Windows: `Windows system assumed buffer larger than it is, events have likely been missed`. This error message appears on the command line during long-running jobs on Windows.
463
+
441
464
### 7.6.0.3
442
465
443
466
- The flag `--overrideProviderSettings` isn't supported.
0 commit comments