> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/connect-your-technology/about-integrations/creating-test-alerts.md).

# Creating Test Alerts

After you successfully connect to a cloud environment, you can create a test alert to confirm it is working and learn more about how Expel responds to incidents.

To do this, you'll take a simple action in your cloud environment. Then, follow the instructions below for your Cloud integration, and receive an email from Expel that shows you what we would do if it were a real incident.

{% tabs %}
{% tab title="Google Cloud Platform (GCP)" %}
Create a temporary Google Cloud Platform (GCP) project and we'll produce an incident as if it were malicious activity. You don’t have to put anything in the project.

There's nothing inherently malicious in creating a GCP project; this is just an easy way to simulate how Expel responds to actual malicious events.

To create a test alert:

1. Go to the [GCP Cloud Resource Manager](https://console.cloud.google.com/cloud-resource-manager).
2. Select **Create Project**.
3. Give the project an ID that starts with `expeltestproject`. Project names in GCP must be globally unique, so try something like **expeltestproject-x8yf92f**, but vary the characters at the end.
4. Fill in the billing account, organization, and a location that makes sense.
5. Select **Create**.

   Within 10-15 minutes, you get an email from <soc@expel.io> with the subject line "*Findings ready for review"*.
6. Select the link in that notification to see the findings report.

{% hint style="info" %}
You can shut down the project immediately after creating it.
{% endhint %}
{% endtab %}

{% tab title="Microsoft Azure" %}
Create an Azure Automation Account named `expeltestautomation`, and we'll produce an incident as if this were malicious activity. You don’t have to do anything in the automation account.

There's nothing inherently malicious in creating an automation account; this is just an easy way to simulate how Expel responds to actual malicious events.

To create a test alert:

1. Log in to the [Azure portal](https://portal.azure.com/).
2. From the top menu, select **+ Create a resource**.
3. Under Categories, select **IT & Management Tools**, and then select **Automation**.
4. Select **Create**.
5. Select a Subscription and Resource Group.
6. Type the Automation account name `expeltestautomation`.
7. Select a Region.
8. Select **Review + Create**, then **Create**.

   Within 10-15 minutes, you get an email from <soc@expel.io> with the subject line "*Findings ready for review*".
9. Select the link in that notification to see the findings report.

{% hint style="info" %}
You can delete the automation account immediately after creating it.
{% endhint %}
{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.expel.io/connect-your-technology/about-integrations/creating-test-alerts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.